Setting Up Okta SSO
Learn how to set up Single Sign-On (SSO) between Okta and CoreStack.
Feature Overview
Okta SSO integration is a Platform-level identity configuration in CoreStack that lets your users authenticate into the CoreStack portal using their existing Okta credentials instead of a separate CoreStack password. It is relevant when your organization standardizes application access through Okta and wants CoreStack included in that single sign-on scope.
This setup is most valuable to Platform Admins and IT/Identity administrators who manage both the Okta tenant and the CoreStack environment configuration. It does not cover SSO configuration for other identity providers, such as Azure AD or OneLogin — those follow separate connection setup processes.
Note: You need the Auth0 tenant name assigned to your specific CoreStack environment before you begin. This value differs by environment (Prod US, Prod MEA, Prod IND, and others) and some environments — such as Prod EU — do not currently support this connection type.
How It Works
You create a SAML 2.0 application in Okta using two CoreStack-provided values — the Single Sign-On URL and the Audience URI — both derived from your environment's Auth0 tenant name and your company name. Once the application is configured and attributes are mapped, Okta generates a SAML certificate and a Sign-On URL. You send these, along with your organization's email domain, to CoreStack support, who use them to activate the connection. The integration is not self-service end-to-end — activation requires CoreStack support to complete the final step, so plan for a short turnaround between submitting your details and SSO going live.
Prerequisites
Before you begin, ensure the following:
- Role: You have the Platform Account Admin role (or equivalent Okta Super Administrator access) to create and configure applications in Okta.
- Environment details: You know which CoreStack environment your organization uses (for example, Prod US or Prod IND) and its corresponding Auth0 tenant name (see the table below).
- Company identifier: You know your company's CoreStack customer name, suffixed with -prod (for example, abc-prod), to use as the
value. - Access: You can access Applications > Applications in the Okta Admin Console.
You'll need the following two configuration values for your CoreStack environment.
Single Sign-On URL:
https://<auth0_tenant_name>-auth.corestack.io/login/callback?connection=<customername>-okta-saml
Audience URI (SP Entity ID):
urn:auth0:<auth0_tenant_name>:<customername>-okta-saml
Auth0 Tenant Names by Environment
Replace <auth0_tenant_name> above with the value for your environment:
| Env Name | Auth0 Tenant Name |
|---|---|
| Prod US | cs-prod-us |
| Prod EU | not enabled |
| Prod MEA | cs-prod-mea |
| Prod IND | cs-prod-indiasaas |
| Prod MSPROD | cs-prod-ms |
| Prod US3 | cs-prod-us3 |
| Prod USEast | cs-prod-us-east |
| Prod US4 | cs-prod-us4 |
Replace <customername> with your company name, appended with "-prod" (e.g. abc-prod).
Step 1: Create the Application in Okta
- In Okta, navigate to Applications → Applications
- Click Create App Integration
- Select SAML 2.0
- Click Next
- Enter the App Name as:
<customername>
Step 2: Configure SAML Settings
Enter the values from the Prerequisites section above:
Single Sign-On URL:
https://<auth0_tenant_name>-auth.corestack.io/login/callback?connection=<customername>-okta-saml
Audience URI (SP Entity ID):
urn:auth0:<auth0_tenant_name>:<customername>-okta-saml
Step 3: Configure Attributes
Add the following Attribute Statements:
| Attribute Name | Value | Notes |
|---|---|---|
application | <customername> | Use the same name used in the app name above. |
email | user.email | Maps your email to CoreStack. |
Step 4: Review and Finish
- Click Next
- Select the appropriate option (Internal app)
- Click Finish
- Save the configuration
- Assign the users who need to sign in to the CoreStack portal through this application
Step 5: Share Your SAML Details
Once the application is set up, Okta will generate two values you need to send to CoreStack support to activate the connection:
- SAML Certificate
- Sign-On URL
Along with these, also share the email domain for which Okta SSO is being configured (e.g. @yourcompany.com).
Step 6: Connection Activation
CoreStack will use these details to activate the connection and confirm once SSO is live and ready to use.
Note: The SAML certificate, Sign-On URL, and email domain are all required to activate the connection — setup cannot be completed without them.
Updated about 4 hours ago