> For the complete documentation index, see [llms.txt](https://docs.fylr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fylr.io/for-system-administrators/integration/authentication.md). # Authentication fylr can use the following authentication services (a.k.a. SSO - Single Sign On) to: * Authenticate user logins. Then your users can log into fylr with their existing credentials. * Apply group membership for rights management. * Retrieve user records: email address, display name, etc.. ### LDAP fylr can be connected to multiple LDAP servers. With or without TLS. Typically, a bind user (a.k.a. machine user) is used to allow the connection. See [our tutorial](/tutorials/auth/ldap.md). ### SAML fylr can be configured to be a Service Provider against a SAML IDP.\ In other words: fylr can be connected to e.g. Shibboleth IDPs and Microsoft Azure Active Directory via SAML. See [our tutorial](/tutorials/auth/saml.md). ### Shibboleth Shibboleth IDentityProviders can be connected via SAML to fylr, which then is a ServiceProvider. See [our tutorial](/tutorials/auth/saml.md). ### Active Directory Microsoft Active Directory, as used in a Local Area network, can be connected via LDAP. See [our LDAP-tutorial](/tutorials/auth/ldap.md). Microsoft Azure Active Directory can be connected via SAML to fylr. See [our SAML-tutorial](/tutorials/auth/saml.md). ### Kerberos Kerberos is not supported by fylr. But if it is used in an Active Directory, LDAP can be connected instead. See [our LDAP-tutorial](/tutorials/auth/ldap.md). ### OpenID We don’t support authentication against OpenID IDPs yet. ### OAuth fylr is usually configured to accept multiple OAuth2 clients and you can add more (fylr in the server role).\ \ We don’t support authentication against OAuth IDPs yet (fylr in the client role). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.fylr.io/for-system-administrators/integration/authentication.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.