Okta
Our Okta app integration is still under review.
This guide explains how to configure Okta as an Identity Provider for your organization to access the Requirement Yogi standalone application using our official app from the Okta Integration Network (OIN).
Prerequisites
You need an administrator account on your Okta organization.
Supported features
SP-initiated SSO (Single Sign-On) : This authentication flow occurs when the user attempts to log in to the application from the Requirement Yogi standalone application.
Just-In-Time provisioning : This means that we automatically create user accounts in the Requirement Yogi standalone application for your Okta users the first time they log in using the Single Sign-On.
Configuration steps
Step 1 - Add the app from the OIN catalog
Navigate to your Okta Admin Console
Navigate to
Applications>ApplicationsClick
Browse App CatalogSearch for
Requirement Yogiand select it from the resultsClick
Add IntegrationYou should be redirected to the general settings of the application
You will be asked to provide the following variables:
Data residency region: EU or US
EUif you are using app.requirementyogi.comUSif you are using app.us.requirementyogi.com
Okta subdomain: The subdomain of your Okta organization
For example, if your Okta domain is
https://acme-corp.okta.com, then your Okta subdomain isacme-corp.
Note down these values for the next steps.
Click
Done.
Step 2 - Assign users or groups
Only users and groups assigned to the application in Okta will be able to sign in.
Navigate to
Applications>ApplicationsSelect the newly added
Requirement YogiapplicationNavigate to the
AsssignmentstabClick
AssignChoose
Assign to PeopleorAssign to GroupsSelect the users or groups that should have access to Requirement Yogi
Click
Save and Go BackClick
Done
Step 3 - Copy your Okta application credentials
Once the application is added, you need to retrieve the credentials to complete the setup.
Navigate to
Applications>ApplicationsSelect the newly added
Requirement YogiapplicationNavigate to the
Sign OntabScroll to
Settings>Sign on methods>OpenID ConnectNote down the following values for the next steps:
Client ID
Client secret
Step 4 - Contact the support to enable the integration
Navigate to our Support page
Choose
GeneralandConfigure an identity providerCreate a new ticket (e.g.
Configure Okta integration for [COMPANY NAME])You will be asked to provide the following details:
Data residency region (
EUorUS)Your email domain (for example,
@acme.com)Your Okta domain (for example,
https://acme-corp.okta.com)Your Okta subdomain (for example,
acme-corp)Client ID (from the previous step)
Client secret (from the previous step)
For security reasons, we may ask you to confirm the ownership of the email domain.
Then, our team will configure the authorization server to use your identity provider for the provided email domain.
Note:
For now, the process of configuring an identity provider is manual. In the future, we plan to build a dedicated interface to help you manage the identity providers of your organization directly from the standalone application.
Step 5 - Test the integration
Once the support team has processed your ticket:
Open a private/incognito browser window
Navigate to the standalone application
Click
Log inYou should be redirected to the login page of the standalone application
Provide the email address of an Okta user that has been assigned to the Okta application
You should be redirected to your Okta SSO portal
Authenticate using the credentials of the Okta user
You should be redirected to the standalone application
Navigate to
Settings>ProfileConfirm that the user details are correct
SP-initiated SSO
Navigate to the standalone application
Click
Log inYou should be redirected to the login page of the standalone application
Provide the email address of your Okta user
You should be redirected to your Okta SSO portal
Authenticate using your Okta credentials
You should be redirected to the standalone application
Troubleshoot
If you encounter any issues or have any questions, feel free to contact our support team.