Skip to main content
Feedback

Setting up Okta as an IdP

To set up Okta as an IdP for Boomi Connect, you must first set up an application in Okta and gather its connection details. Then, register the application as an IdP in Boomi Connect.

Prerequisites

Make sure that you fulfill the following requirements before you start creating an IdP in Boomi Connect for your Okta application.

  • An Okta account with administrator access to the Okta Admin Console.

  • An OIDC web application created in Okta, with access assigned to the desired users or groups. Refer to Create OpenID Connect app integrations for information about creating an OIDC web application in Okta.

    • If you allow access for everyone in your organization, make sure you also select the Enable immediate access with Federation Broker Mode check box. Refer to Enable Federation Broker Mode for information about enabling the Federation Broker Mode in Okta.

  • The Client ID and Client Secret values from the Okta application's Client Credentials section. If more than one client secret exists for your application, copy the one with Active status in Client Credentials. Refer to Find your application credentials for information about locating these values in an Okta application.

  • Your Okta domain used to construct the IdP's well-known URL. Refer to Find your Okta domain for information about finding your Okta domain.

  • Boomi Connect's callback URL added to the application's sign-in redirect URI in Okta. The URL follows the pattern {environment-domain}/oauth/identityprovider/oauth/callback. For example, for the US production environment, this URL is https://us.bc.boomi.com/oauth/identityprovider/oauth/callback. Only the domain changes between environments. The path segment, /oauth/identityprovider/oauth/callback, remains the same. Refer to OpenID Connect (OIDC) Sign-in Redirect URI for information about configuring sign-in redirect URIs in an Okta application.

Configuring Okta IdP for Boomi Connect

  1. Log in to the Boomi Connect environment that matches the callback URL you registered in your Okta application. For example, if the callback URL you registered points to the US production environment, us.bc.boomi.com, log into Boomi Connect on that environment.

  2. On the left sidebar, click Identity Providers.

  3. On the Identity Providers page, click Add Identity Provider.

  4. In the Add Identity Provider form, provide the following information:

    1. For Name, enter a name for the IdP. This name is arbitrary and used only within Boomi Connect.

    2. For Well-Known URL, enter the URL by substituting your domain value in this template: https://{yourOktaDomain}/.well-known/openid-configuration, where {yourOktaDomain} is your Okta application's domain value. For example, given the domain dev-12345678.okta.com, the well-known URL is https://dev-12345678.okta.com/.well-known/openid-configuration. This template assumes Okta's built-in org authorization server. The well-known URL might differ if you use a different authorization server. Refer to Authorization servers for more information about the well-known URL format.

    3. For Client ID, enter the unique identifier from your Okta application’s Client Credentials section.

    4. For Client Secret, enter the confidential credential your Okta application uses to authenticate itself with Okta. You must keep this credential a secret because exposure allows unauthorized token issuance.

    5. Click Add Provider.

The new Okta IdP appears as a tile on the Identity Providers page and is ready to use.

On this Page