Configuring SAML single sign-on
Before changing your single sign-on configuration
Changes to your single sign-on configuration can result in your team members, including admins, being locked out of the Celonis Platform. We recommend that before changing your single sign-on configuration, you enable Allow bypassing via login form (step 3 below) for your current configuration. This allows users who are outside of your identity provider to still access your team with an email address and password in the event of a misconfiguration.
Your users can access your Celonis Platform using their existing login credentials by configuring SAML SSO for your team. This process establishes a trust relationship between the Celonis Platform and your existing identity provider (IdP), authenticating the user when they login to the platform.
Your Celonis Platform team environment supports SAML 2.0 with the SHA-256 hash algorithm. It doesn't support SAML logout functionality or identity provider initiated flows, however.
When configuring your SAML SSO, you must select your preferred certificate management method (step 4). For more information about your options here, see Certificate management for SAML SSO
When configuring your external identity provider, see: External identity provider configuration
Configure and activate your SAML SSO:
To configure and activate your SAML SSO:
Click Admin & Settings - Single Sign-On.
Click SAML - Configure.
Configure your general settings, including a name and provider name.
You can also configure the following options here:
Maximum Authentication Life Time: This enables you to control how long the user remains signed in (minutes), with the default set to 480 mins (8 hours). After this time, the user must sign-in again with their identity provider to regain access to your Celonis Platform .
If this option is disabled, the maximum period allowed by the Celonis Platform is 10 years. Typically this means that the timeout period is defined and configured on your identity provider.
Allow bypassing via login form: Enabling this option allows users who are outside of your identity provider to still access your team with their email address and password. This feature is beneficial when working on implementation projects or when adding the user to your identity provider is not possible. You can also enable this option if you need to give a member of the Celonis Support team access to your environment to problem solve.
When bypassing via login form, your login from can be accessed via the following URL format:
https://<team>.<realm>.celonis.cloud/ui/login
Select your certificate type (uploading a user-provided certificate if necessary).
See: Certificate management for SAML single sign-on
Upload your identity provider's metadata. The metadata is an XML file representing the configuration of your SSO and should be available for download in the SSO’s admin interface.
You can also use the following features here:
Download SP Metadata: The service provider (SP) metadata file allows for quick configuration on the identity provider and is available once you have uploaded your identity provider metadata file.
Enable SP Metadata Access via Public URL: This gives you access to a link that reduces the manual effort involved when certificate changes are needed. Depending on your identity provider, this link can enable you to automatically update the certificate when required and without accessing the Celonis Platform to do so.
Click Save.
When prompted, either click Activate or choose to activate your configuration later.
Your SAML SSO is now active, with all active users at that point being automatically logged out of your Celonis Platform .They’ll need to re-authenticate to regain access.
External identity provider configuration
Note
The following external identity providers have been successfully configured with Celonis: Microsoft Azure, Okta, OneLogin, ADFS, and JumpCloud. For detailed instructions on how to configure these providers, refer to their documentation.
When configuring your SAML SSO on your external identity provider, the following fields information may be needed:
Relying Party Trust Identifier (also referred as entityID, Identifier, or Audience)
Use the following format:
<team>.<realm>.celonis.cloud
For example: testcompany.eu-1.celonis.cloud
Relying Party Identity Provider Endpoint (also referred as Reply URL or Recipient)
The login type should be: SAML Assertion Consumer.
And the endpoint should be provided in this format:
https://<team>.<realm>.celonis.cloud/api/auth-handler/saml/callback?client_name=SAML2Client
For example: https://testcompany.eu-1.celonis.cloud/api/auth-handler/saml/callback?client_name=SAML2Client
Login URL
As your SAML SSO configuration can't be tested within your Celonis platform team, you should use the following URL format to access the platform:
https://<team>.<realm>.celonis.cloud/
For example: https://testcompany.eu1.celonis.cloud/
Celonis platform signed authentication requests
To enable your Celonis Platform to sign authentication requests sent to your identity provider you must set your WantAuthnRequestsSigned attribute to 'true'.
For example:
<md:IDPSSODescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol" WantAuthnRequestsSigned="true">User Attributes and Claims - custom email assertion
For many identity providers (such as Azure), you must create a custom "email" assertion to the User Attributes and Claims section.
Azure AD: By default when you add a new claim in Azure AD, the namespace is set to:
http://schemas.xmlsoap.org/ws/2005/05/identity/claims.
Delete this default setting and leave the namespace field empty.
The new claim "email" must be lowercase and mapped with an email address field from the source, as individual users in Celonis are must have unique email addresses.