Managing Single Sign-on Integration with Okta

With Single Sign-on (SSO) integration, you no longer need to create individual username and password-based accounts for Metacloud users. This allows for easier integration across groups of users and different organizations in your environment, since users maintain a single login and password across various tools in your environment.

There is no longer a need to provision user entries in Identity service, since the user entries already exist in the Identity Provider’s (IdP) databases. A common identity store is useful as it can be set up properly once and used in multiple places.

With single sign-on, a user uses the credentials that are provided and maintained by the user’s Identity provider to access different services in their environment.

Single sign-on is easier and faster for users and requires fewer password resets. Users can spend too much time logging in or going through ‘Forgot Password’ workflows. The IdPs manage user identities and passwords so Metacloud does not have to.

Administrators can manage roles at the group level instead of the individual user level on the Dashboard, making onboarding easier as a user’s group memberships are managed centrally through your IdP tool.

To set up single sign-on integration, see Setting Up Single Sign-on Integration.