Instructions for

Enable Express Configuration

This guide walks you through how to enable Express Configuration for your Auth0-enabled

OIN integration and verify the setup to ensure successful integration.

What you need

An Okta Integrator Free Plan org (opens new window)
An admin user in the org with either the super admin role or the app and org admin roles
Auth0-enabled SaaS app that supports OIDC capability
Auth0 Enterprise subscription with the Auth0 Organizations (opens new window) feature enabled
Auth0 Command Line Interface (opens new window)(CLI) permission

Authenticate with Auth0 CLI

To get started with Express Configuration, you need to authenticate with the Auth0 CLI (opens new window). This establishes a connection between your app environment and your Auth0 tenant. Run the following command to authenticate with the Auth0 CLI with the right scopes.

Note: Before you run the command, replace $AUTH0_DOMAIN with your Auth0 tenant's domain. For example, your-tenant.us.auth0.com.

auth0 login --domain $AUTH0_DOMAIN --scopes update:tenant_settings --scopes create:client_grants --scopes create:client_credentials --scopes update:client_credentials

The specified scopes ( create:client_credentials, update:client_credentials, create:client_grants, and update:tenant_settings) provide the CLI permissions to modify tenant-wide settings and create client grants, which are essential for the subsequent configuration steps.

Create a resource server in Auth0

The resource server refers to the Okta Express Configuration API. When you authorize Okta for this resource server using OAuth 2.0, Okta receives an access token and uses it to access user and org information.

Run the following command to create the resource server (opens new window) in Auth0:

Note: The identifier parameter is a unique URI that identifies the resource server. The expressconfigure:sso scope allows Okta to configure SSO settings.

auth0 api post resource-servers \
  --data '{
    "name": "Okta Express Configure API",
    "identifier": "https://system.okta.com/actions/express-configure/v1",
    "scopes": [
      {
        "value": "expressconfigure:sso",
        "description": "Configure SSO with Express Configuration"
      }
    ],
    "enforce_policies": true,
    "token_lifetime": 300,
    "allow_offline_access": false,
    "skip_consent_for_verifiable_first_party_clients": false
  }'

Configure roles and permissions

Follow these steps to configure the roles and permissions required for managing Express Configuration.

Create a role

Run the following command to create a role (opens new window) for users who manage the Express Configuration integration. This command creates a role named EXPRESS_CONFIGURE_ADMIN_ROLE.

Note: Skip this step if you already have a suitable role for managing Express Configuration.

auth0 roles create \
  --name "EXPRESS_CONFIGURE_ADMIN_ROLE" \
  --description "Administrator role for Express Configuration"

Assign permissions to the role

Assign the expressconfigure:sso permission to the specified role. Replace $ROLE_ID with the role ID that you want to grant permission to.

auth0 roles permissions add "$ROLE_ID" \
  --api-id "https://system.okta.com/actions/express-configure/v1" \
  --permissions "expressconfigure:sso"

Create and assign Client Credentials

Create a client

Run the following command to create a client. Ensure that you provide configuration values that are specific to your app.

Notes:

The express_configure_sp_client_id value refers to the client ID of the app that you're enabling Express Configuration for.

The organization_usage value ensures that users sign in using an org. Set this value to true, as it’s a prerequisite for Express Configuration. Setting the value to true ensures that Express Configuration functions within the context of an org, which provides secure and structured access control.

The organization_require_behavior value determines how the org's sign-in behavior is handled. See Define Organization Behavior (opens new window).

Save the public key provided by Okta Express Configuration in the okta-public-key.pem file.

Ensure that you make note of the Okta OIN Integration Client app client ID after it’s created. Share this client ID with the Okta Express Configuration team to configure your app in the OIN.

auth0 api post clients \
  --data '{
    "name": "Okta OIN Integration Client",
    "description": "For Okta OIN Integration",
    "app_type": "regular_web",
    "callbacks": ["https://system-admin.okta.com/admin/app/generic/oauth20redirect"],
    "oidc_conformant": true,
    "grant_types": ["authorization_code", "client_credentials"],
    "jwt_configuration": {
      "alg": "RS256"
    },
    "client_authentication_methods": {
       "private_key_jwt": {
         "credentials": [
           {
              "name": "OIN Public Key",
              "credential_type": "public_key",
              "pem": '"$(jq -Rs '.' ./okta-public-key.pem)"',
              "alg": "RS256"
           }
         ]
       }
    },
    "organization_require_behavior": "post_login_prompt",
    "organization_usage": "require",
    "client_metadata": {
      "express_configure_sp_client_id": "'$SERVICE_APP_CLIENT_ID'"
    }
  }'

Assign Client Credentials to the Okta OIN Integration Client

Use this Client Credentials to authorize the Okta OIN Integration Client to access the Auth0 Management API with defined scopes. The OIN can use the token that's returned to create and manage connections on behalf of the orgs. The scopes (create:connection, update:connection, and so on) securely allow your Auth0 tenant's Management API to create and update Okta Workforce connections (opens new window).

Run the following commands to create the Client Credentials. Ensure that you update the client_id value with the OIDC app client ID and include the Auth0 domain in the audience parameter.

auth0 api post client-grants \
  --data '{
    "client_id": "'$OIN_APP_CLIENT_ID'",
    "audience": "https://'$AUTH0_DOMAIN'/api/v2/",
    "scope": [
      "create:connections",
      "read:connections",
      "update:connections",
      "read:connections_options",
      "update:connections_options",
      "read:organization_connections",
      "create:organization_connections",
      "update:organization_connections"
    ]
  }'

Configure and deploy an action

Create a custom post-login action (opens new window) to add custom claims (sp_client_id, management_api_audience, and init_login_uri) to the access token that Auth0 issues after a user successfully signs in. These claims provide Okta with the necessary information for the Express Configuration process.

Create a file named add_post_login_action.js and add the following code:


    exports.onExecutePostLogin = async (event, api) => {

    if (event.request.query.audience !== event.secrets.EXPRESS_CONFIGURE_API_IDENTIFIER) {
       return;
    }

    if (!event.client.metadata.express_configure_sp_client_id
        || !event.organization?.id) {
      throw Error("Unable to issue token for Express Configure API - missing data.");
    }

    // this is the client id of service app
    api.accessToken.setCustomClaim('sp_client_id', event.client.metadata.express_configure_sp_client_id);
    api.accessToken.setCustomClaim('management_api_audience', event.secrets.TENANT_DOMAIN + '/api/v2/');

    const loginUri = event.secrets.SERVICE_INIT_LOGIN_URL;
    api.accessToken.setCustomClaim('init_login_uri', loginUri);
  };

Run the following command to create the express_configure_postlogin_action post-login action that's triggered after a user logs in.

Replace the following values:

SERVICE_INIT_LOGIN_URL: The URL that the end users use to sign in to your app. For example, https://example.com/login.
$AUTH0_DOMAIN: Your tenant domain.

auth0 actions create \
  --name "express_configure_postlogin_action" \
  --trigger "post-login" \
  -r "node22" \
  -s "SERVICE_INIT_LOGIN_URL='$SERVICE_INIT_LOGIN_URL'" \
  -s "EXPRESS_CONFIGURE_API_IDENTIFIER=https://system.okta.com/actions/express-configure/v1" \
  -s "TENANT_DOMAIN=https://$AUTH0_DOMAIN" \
  --code "$(cat ./add_post_login_action.js)"

Deploy the action

Run the following command to deploy the action. Select the action from the prompt for the Express Configuration created in the [previous step].

auth0 actions deploy

Attach the action to a flow

Attach the action to a flow so that it executes as part of your tenant's traffic. See Auth0 Actions (opens new window) to add an action using the Auth0 dashboard.

auth0 api patch \
  actions/triggers/post-login/bindings \
  --data '{
    "bindings": [
      {
        "ref": {
          "type": "action_name",
          "value": "express_configure_postlogin_action"
        },
        "display_name": "express_configure_postlogin_action"
      }
    ]
  }'

Update tenant settings

Note: Okta recommends completing this step even though it's not required to enable Express Configuration.

Update tenant settings to display the scope details on the consent page. These settings improve the user experience by providing information about the permissions being granted. Use the use_scope_descriptions_for_consent parameter to ensure that scope descriptions are shown instead of raw scope names.

auth0 api patch tenants/settings \
  --data '{
    "flags": {
      "use_scope_descriptions_for_consent": true
    }
  }'

Email the Okta Express Configuration team

Email the following information to the Okta Express Configuration team at expressconfig@okta.com:

Confirmation that you completed all the steps in this guide and that your app is ready to support Express Configuration.
Your app name in the OIN
Okta OIN Integration Client app client ID

The Okta Express Configuration team configures your app in the OIN and then assigns it to your Okta Integrator Free Plan org.

You can test the feature by creating an instance of your app in the OIN catalog.

Verification and testing

Follow these steps to verify and test the Express Configuration feature:

Sign in to your org as a user with either the super admin (SUPER_ADMIN) role, or the app (APP_ADMIN) and org (ORG_ADMIN) admin roles (opens new window).
Go to Applications > Applications in the Admin Console.

Additional information

Edit This Page On GitHub