Knowledge Base/How to configure SSO with Uniform

How to configure SSO with Uniform

IntegrationDeveloperSecurity

Uniform.app integrates with any identity provider considering it supports OpenID Connect or SAML 2.0 standard. Consult this guide to initiate setup, provide your Uniform technical account representative with the following information depending on the provider.

  1. Pick a desired connection name - this should be a short, unique string for your company.
  2. Send a request to enable SSO to Uniform Support.
  3. Support will confirm the assignment of the connection name, which will dictate the following information that can be used to setup your SAML connection with Uniform.
    • SAML Unique Identifier: urn:auth0:uniformsystems:[your-connection-name]
    • Reply URL: https://login.uniform.app/login/callback?connection=[your-connection-name]
    • Logout URL: https://login.uniform.app/logout
  1. Pick a desired connection name - this should be a short, unique string for your company.
  2. Send a request to enable SSO to Uniform Support. Provide the team at Uniform with the following information:
    1. Sign in URL - this is generated by the SSO provider.
    2. x509 signing certificate - SAMLP server public key encoded in .pem or .cer format.
    3. Email domains to be handled - the domains for the email addresses that will be used to log into Uniform. This is the value after the @ in your email address.
  3. Support will confirm the assignment of the connection name and communicate next steps.

In addition, Uniform expects the name assertion from this for a SAML connection - and that the rest of these assertions can/should be used to push user metadata into our system.

{ "user_id": [ "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier", "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn", "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"], "email": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress", "name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name" }

TODO

Last modified: February 5, 2025