Propensity supports authentication through Okta using OpenID Connect (OIDC). To enable Okta sign-in, you must create and configure an application in Okta and provide the required credentials to Propensity.
Set up Okta sign-in with Propensity
To set up Okta sign-in with Propensity, you must create an application in Okta.
To create a connection to Okta, you will need the following information:
Client ID
Client Secret
Okta organization domain
Create an Okta application
If you do not already have an Okta application, you must create one.
Create a new Web Application in Okta using the Okta-provided tutorial. Follow the steps in the guide below to create the application:
Tutorial:
https://developer.okta.com/docs/guides/sign-into-web-app/nodeexpress/create-okta-application/
Once you complete the tutorial, record your Client ID, Client Secret, and Okta organization domain.
When configuring your Okta application, enter the following URL as both the Login redirect URI and Initiate login URI:
https://auth.propensity.com/oktaUse an existing Okta application (optional)
If you already have an Okta application with OpenID Connect enabled, you can skip the application creation steps.
In this case, record the required Okta credentials from your existing application (Client ID, Client Secret and Okta organization domain).
Share credentials with Propensity
Provide your Propensity contact with the following information:
Client ID
Client Secret
Okta organization domain
Alternatively, you can reach out to Propensity support via Live Chat for assistance.
User auto-provisioning with Okta
Propensity supports automated user provisioning when Okta is used for authentication.
When auto-provisioning is enabled, user access is managed entirely through Okta.
How auto-provisioning works
A user is granted access to the Propensity application inside Okta.
The user logs into Propensity using the Okta OAuth login flow.
A Propensity user account is automatically created for that Okta user.
The user can immediately access Propensity after authentication.
User deactivation
When a user is deactivated or removed from the Propensity application in Okta:
The user can no longer authenticate into Propensity.
Access to Propensity is automatically revoked.
Manual user creation or removal in Propensity is not required when Okta is used as the identity provider.
Notes and considerations
Auto-provisioning is triggered on first successful login
User access is controlled by Okta application assignments
Propensity does not require manual user management when Okta is the identity provider