SAML Applications
Each SAML Application represents an integration between your tenant and an application (sometimes called "Service Provider", or "SP") that uses SAML for authentication.
SAML Applications are configured using metadata, which is provided by the application owner. This metadata defines how the application and your tenant communicate and trust one another, including details such as the application’s Entity ID, Assertion Consumer Service (ACS) URL, supported bindings, & certificates used to secure authentication responses.
Each SAML application is managed independently. Changes affect only that specific integration, and determine how authentication is processed for the associated application.
Use caution when modifying metadata. Updates to metadata are applied to the tenant as soon as possible & may disrupt authentication if configured incorrectly. We recommend saving a copy of existing metadata before making changes.
Add SAML Application To Bridge Or Proxy
Sign in to the Cirrus Console.
Once signed in, select the gear next to the tenant you want to update.
Scroll to the “Applications” section.
You will be able to adjust your view to only your SAML applications.
Use the “+ Add SAML Application” option under “Configuration”.
Select the appropriate metadata source (Remote or Managed by Cirrus).
Provide the required metadata.
Once finished, save your configuration.
Configure Application To Trust Bridge Or Proxy
Sign in to the Cirrus Console.
Once signed in, select the gear next to the tenant you want to view.
Use the “Configure Application” option under “Configuration”.
This will open a view of SAML configuration details for your tenant.
Save these values for use with your application.
Apply the values in your app's configuration, or pass it the Bridge/Proxy metadata URL.
The available configuration options for SAML application metadata vary by tenant type. Depending on the tenant you are managing, your view may include different configuration settings than those in this guide.