Opsera supports Okta to Okta account federation via Okta OpenID Connection (OIDC). In this process, both Organizations must use Okta for their user identify management. The customer will be responsible for configuring an External Identify Provider in their Okta account and share that with Opsera. Once complete all authentication will be managed through the customer’s Okta via Federated Identity.
...
Values Required for Customer to setup their SSO
Sign-in redirect URI’s: (make sure both are registered)
https://portalopsera.opsera.io/authorization-codeokta.com/oauth2/v1/authorize/callback
https://portal.opsera.okta.com/oauth2/v1/authorizeio/authorization-code/callback
Sign-out redirect URI’s:
Base URI’s:
...
Ensure users have access TO the app in your SSO
Please ensure BOTH sign-in redirect URI’s are included in this setup, otherwise it will fail.
What you must send Opsera (after you complete your setup):
...
Configure the new APP with these values:
Client acting on behalf of user: Authorization Code
Sign-in redirect URI’s:
Sign-out redirect URI’s:
Base URI’s:
Assignments*: Controlled access: Up to you to choose as the SSO Admin but users MUST have this access in order to log in.
Please ensure BOTH sign-in redirect URI’s are included in this setup, otherwise it will fail.
| Note |
|---|
*Assignments: You must ensure users are granted access to the new Application created in Okta if you want them to be able to log into Opsera. |
...