deployment

No menu items for this category

SAML SSO

  • Every IDP will have the following information
  1. EntityId/Authority -> Same as IDP Openmetadata has an Entity Id
  2. SignOn Url -> Service Provider SignOn Url
  3. X509 Certificate -> In case the SP expects (wantAuthnRequestSigned) then provide certificate for validating.
  4. Authority Url -> We just need to update the domain localhost.
  5. NameID: This is sent as part of request and is provided by the IDP.

Every IDP provides this information, we can download the XML Metadata and configure the OM taking the values from the XML.

  • Openmetadata is the service provider, we just update the localhost to the hosted URI.
  1. EntityId/Authority -> Normally a Url providing info about the provider.
  2. SignOn Url -> Url to be used for signing purpose.
  3. X509 Certificate -> In case the SP expects a signed response from IDP, the IDP can be configured with Signing Certificate given by SP.
  4. Private Key -> In case SP expects a encrypted response from the IDP , the IDP can be configured with SPs public key for encryption and the Private Key can be used for SP for decrypting.

SP Metadata XML is available at "http://localhost:8585/api/v1/saml/acs", localhost needs to be updated with the correct URI.

Security Configuration controls the SP requirement for the Security related aspects. The SP can be configured to send signed or encrypted or both request , and in return can also expect signed or encrypted or both responses from the IDP.

Jwt Configuration is mandatory for Saml SSO.

More specific details on different IDPs can be found below:

Once your server security is set, it's time to review the ingestion configuration. Our bots support JWT tokens to authenticate to the server when sending requests.

Find more information on Enabling JWT Tokens and JWT Troubleshooting to ensure seamless authentication.