Skip to main content
Give Operata the metadata it needs to enable SAML 2.0 single sign-on (SSO) for your account so your team signs in with corporate credentials instead of an Operata password.

​
Before you start

  • An Operata account with admin permissions.
  • A SAML 2.0 identity provider (IdP) you administer — for example Okta, Azure AD, OneLogin, or Auth0.
  • The list of email domains your users sign in with. Operata routes all listed domains to the same SSO connection.
This guide covers SAML 2.0. For an OpenID Connect (OIDC) identity provider, see Configure an OIDC identity provider for SSO.

​
Steps

​
1. Email Operata Support

Send a request to Operata Support stating that you want to enable SSO. Specify the Operata Group IDs you want SSO on — production, development, test, or all three. Operata replies with a connection name and the SAML configuration values you need to set on your IdP side.

​
2. Create a SAML 2.0 application on your IdP

Create a SAML 2.0 application in your identity provider using the connection name, sign-in URL, and audience restriction Operata supplies. The IdP-specific steps live in: For other IdPs, follow the vendor’s standard SAML 2.0 application setup using Operata’s supplied URLs.

​
3. Export the SAML metadata

Export the SAML metadata XML from your IdP. If your IdP does not support XML export, capture the following values instead:
  • Sign-in URL.
  • X.509 signing certificate in PEM or CER format.
  • The email domains that sign in through this connection.

​
4. Send the metadata to Operata

Reply to the support thread from step 1 with the metadata XML (or the three values from step 3). Operata creates the SSO connector and replies when it is ready to test.

​
5. Joint test with Operata

Operata schedules a call to switch your platform IdP over to the new connector and verifies SSO sign-in end to end with you on the call. Once the test passes, your users sign in through your IdP from then on.

​
Result

A user whose email matches one of the domains you listed visits https://app.operata.io, enters their email, and is redirected to your IdP. After authenticating with corporate credentials, the user lands in the Operata console without entering an Operata password.