SAML 2.0 is the leading standard to implement single sign-on. Cloud Secure Edge (CSE) integrates with your SAML Identity Provider, via the SAML 2.0 HTTP POST binding, to authenticate enterprise users that need access to CSE-secured services.
In order to set up this integration, you need will need administrative access to your SAML Identity Provider and the ability to add a new SAML App.
1.1 Navigate from Settings > Identity and Access tab > End User tab, and then set your User Identity Provider to SAML.
Fill out these Identity Provider configuration fields after you set up the new application integration.
1.2 Take note of the Redirect URL (ACS) provided in the configuration field.
When asked for Callback URL, Assertion Consumer Service (ACS) URL, SP SSO URL, or Recipient SSO URL in the SAML Identity Provider, use the Redirect URL you obtained in Step 1b above.
If you're asked for the RP/SP Entity ID, use the Redirect URL as well.
Ensure the NameID format in your IDP is set to Persistent; Banyan TrustProvider does not support other formats right now.
CSE requires your IDP's returned SAML assertion to contain attributes can be mapped to a user's Email, Username, and Groups.
Configure that mapping in this step, and take note of the names for the Email Attribute, Username Attribute, and Groups Attribute.
Allow CSE to federate authentication of all users in your organization to your SAML IDP.
You still need to apply Policies in the Command Center to manage which users can access specific internal applications.
Note down the data you need to enter in the next step.
6.1 Return to the Identity Provider page in the Command Center (Settings > Identity and Access tab > End User tab) and enter the Banyan TrustProvider App parameters from your SAML IDP:
6.2 Select Update Identity Provider Config to save the settings.
That's it! You have successfully integrated your SAML IDP to manage your directory of users in CSE.