Single Sign On

Atfinity only officially supports SAML via Azure Active Directory. Other providers may work, but have not been tested.
Atfinity can use SAML-based Single Sign on interfaces to authenticate users. To set up Single Sign On, you need access to the Server itself, so this is only available for Enterprise customers or customers using Atfinity deployed on their own premises using our Kubernetes Helm Chart. 
In general, you need a url to your identification providers federation metadata to get started
Getting Started
If you are running Atfinity using Docker Compose, you need to set up these environment variables:
SSO_ENABLED
Boolean
​
SSO_NAME
String
The name displayed to users when logging in, e.g. "MyBank Active Directory"
SSO_METADATA_URL
String
The url to your identification provers federation metadata. This should point to a hosted .xml file containing the service metadata. Usually, these urls end in "federationmetadata.xml"
If you are running Atfinity using our Kubernetes Helm Chart, you have to configure the same values, but provide them as extra Values in the helm chart. The values are called sso.enabled, sso.name and sso.metadataUrl.

Last modified 1yr ago

SSO_ENABLED	Boolean
SSO_NAME	String	The name displayed to users when logging in, e.g. "MyBank Active Directory"
SSO_METADATA_URL	String	The url to your identification provers federation metadata. This should point to a hosted .xml file containing the service metadata. Usually, these urls end in "federationmetadata.xml"