SAML support is widely promoted in many places on the website, such as the homepage and the connectors page.
However there is a big fat bold WARNING on the top of SAML:
The SAML connector is unmaintained, likely vulnerable to authentication bypass vulnerabilities, and is under consideration for deprecation (see #1884). Please consider switching to OpenID Connect, OAuth2, or LDAP for identity providers that support these protocols. If you have domain expertise in SAML/XMLDSig and would like to volunteer to maintain the connector please comment on the discussion.
The project should therefore be more restrained in its visible promotion of SAML support when in reality the support is in-effect in a deprecated state.
I have opened PR #214 in relation to the connectors page. But I really suggest you re-think SAML more broadly, i.e. maybe you want to pull all references to it and drop support if you're not going to be actively maintaining it.
SAML support is widely promoted in many places on the website, such as the homepage and the connectors page.
However there is a big fat bold WARNING on the top of SAML:
The project should therefore be more restrained in its visible promotion of SAML support when in reality the support is in-effect in a deprecated state.
I have opened PR #214 in relation to the connectors page. But I really suggest you re-think SAML more broadly, i.e. maybe you want to pull all references to it and drop support if you're not going to be actively maintaining it.