---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/pt-BR/integrate-applications

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Set up Okta spoke

# Set up Okta spoke {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 min. de leitura

Integrate the Okta spoke with Okta to automate various actions on Okta. For example, you can automate the activation of a user on Okta. To integrate, connect your ServiceNow instance and Okta using an API key or OAuth authentication.

## Antes de Iniciar

* Request Integration Hub subscription.
* Activate the Okta spoke on your ServiceNow instance.
* Account with the Okta developers portal.
* Role required: admin.
{#set-up-okta-v1.1.1__ul_l2l_mph_gfb}

## Por Que e Quando Desempenhar Esta Tarefa

Depending on your requirement, you can set up the spoke using an API key or OAuth credentials. However, you can use only one alias at a time for a ServiceNow domain.

## Set up Okta spoke using API key {#ariaid-title2}

Integrate the ServiceNow instance and your Okta account using an API key to authenticate ServiceNow requests.

### Generate an API key to request authentication {#ariaid-title3}

Generate an API key on your Okta organization or developer account to have the connection record authenticated by the Okta developer's or organizational account.

#### Antes de Iniciar

Okta requirements:

* Okta organization or developer account
* Role required: Okta administrator
{#configure-okta-account-v1.1.1__ul_nhk_cnh_gfb}

#### Por Que e Quando Desempenhar Esta Tarefa

The API key enables the Okta organization or developer account to authenticate an access request from your ServiceNow instance.

#### Procedimento

1. Log in to <https://developer.okta.com/login/>.
2. On the left panel, navigate to SecurityAPI.
3. On the API page, select Tokens.  
4. Select Create token.
5. In the Create token window, enter a name for the token.
6. Select Create token.  
   The token is created.

7. Copy the API token and store at a secured place.  
   Note the expiry date of the token.

{#configure-okta-account-v1.1.1__steps_j3p_ndz_4fb}

### Create an API Key credential record for the Okta spoke {#ariaid-title4}

Create Credential records to the Okta application that you created. The Okta spoke connection and credential alias uses these credentials to authorize actions.

#### Antes de Iniciar

Role required: admin.

#### Procedimento

1. Navigate to AllConnections \& CredentialsCredentials.
2. Select New.
3. Select API Key Credentials.
4. Fill the form.  
   {#create-credential-okta-v1.1.1__table_lwy_g1z_4fb__entry__2}

   | Field | Value required |
   |-|-|
   | Name | A custom name that uniquely identifies the record. For example, <kbd class="ph userinput">Okta Credentials</kbd>. |
   | Active | Activates the credential record so that it's used to connect to the Okta account. |
   | API Key | API token that you had generated in your Okta account in the format `SSWS <API token>`. Replace <kbd class="ph userinput">&lt;API token&gt;</kbd> with the API token. To learn how to generate an API token, see [Generate an API key to request authentication](https://www.servicenow.com/docs/u~JI~zizFhqyagf~3v2EQQ#configure-okta-account-v1.1.1 "Generate an API key on your Okta organization or developer account to have the connection record authenticated by the Okta developer's or organizational account."). |
   | Applies to | MID Server that can use this credential. For example, select All MID Servers. |
   | Order | Order (sequence) in which this credential is used as it attempts to access the Okta API. The smaller the number, the higher in the list this credential appears. Establish credential order when using large numbers of credentials or when security locks out users after three failed login attempts. If all the credentials have the same order number (or none), the instance tries the credentials in a random order. For example, enter <kbd class="ph userinput">100</kbd>. |
   | Credential alias | The credential alias for Okta spoke that resolves in runtime when connecting to the Okta API. |
   [ ]

   {#create-credential-okta-v1.1.1__table_lwy_g1z_4fb}
5. Select Submit.
{#create-credential-okta-v1.1.1__steps_t5s_2fy_4fb}

### Create a connection record for the Okta spoke {#ariaid-title5}

Create a Connection record to the Okta API. The Okta spoke connection and credential alias uses these connections to perform actions in Okta.

#### Antes de Iniciar

Role required: admin.

#### Procedimento

1. Navigate to AllConnections \& CredentialsConnection \& Credential Aliases.
2. Open for the record for Okta.
3. From the Connections tab, select New.
4. Fill the form.  
   {#create-connection-okta-v1.1.1__table_any_shp_gfb__entry__2}

   | Field | Value required |
   |-|-|
   | Name | Enter any name to uniquely identify the connection record. For example, enter <kbd class="ph userinput">Okta Connection</kbd>. |
   | Credential | Select the Credential record that you created for Okta. For example, select Okta Credentials. |
   | Connection URL | Enter your Okta organization URL. For example, <kbd class="ph userinput">https://dev-418994.oktapreview.com</kbd>. |
   [ ]

   {#create-connection-okta-v1.1.1__table_any_shp_gfb}
5. Select Submit.
{#create-connection-okta-v1.1.1__steps_zwz_fhz_4fb}

## Set up Okta using OAuth credentials {#ariaid-title6}

Integrate the ServiceNow instance and your Okta account by creating a custom OAuth application in Okta to authenticate the ServiceNow requests.

### Antes de Iniciar

* Access to the Okta Developer Console
* Role required: admin
{#setup-okta-oauth-cred__ul_czf_cwq_gnb}

### Create an OAuth application in Okta {#ariaid-title7}

Create a custom OAuth application in your Okta developer's account to enable OAuth 2.0 authentication of the requests from your ServiceNow instance.

#### Antes de Iniciar

Role required: admin

Administrator access to Okta Developer's or Organization account

#### Procedimento

1. Log in to <https://developer.okta.com/login/>.
2. On the left panel, select ApplicationsApplications.
3. On the Applications page, select Create App Integration.  
4. On the Create a new app integration window, select OIDC - OpenID Connect.
5. Select  
   * OIDC - OpenID Connect
   * Web Application
   {#conf-okta-app__ul_hgb_xzg_wyb}
6. Select Next.
7. Fill the form.  
   {#conf-okta-app__table_jwz_52h_wyb__entry__2}

   | Field | Description |
   |-|-|
   | App integration name | Custom name of the OAuth application. |
   | Logo | Logo of the OAuth application. Uploading a logo is optional. |
   | Grant type | The type of OAuth 2.0 flow to use depending on the type of application you're building. To learn how to select the appropriate option, see <https://developer.okta.com/docs/concepts/oauth-openid/#openid-connect>. Select the options: * Authorization Code * Refresh Token * Implicit (Hybrid) * Allow ID Token with implicit grant type * Allow access token with implicit grant type {#conf-okta-app__ul_mjd_dwh_wyb} {#conf-okta-app__ul_ljd_dwh_wyb} |
   | Sign-in redirect URIs | The URI that receives the authentication response and ID token from Okta. Enter your ServiceNow instance URL in the format <kbd class="ph userinput">https://&lt;instance-name&gt;.service-now.com/oauth_redirect.do</kbd>. |
   | Sign-out redirect URIs | The URI that contacts Okta to close a user session. Enter your ServiceNow instance URL in the format <kbd class="ph userinput">https://&lt;instance-name&gt;.service-now.com/oauth_redirect.do</kbd> |
   | Base URIs | URI of the self-hosted Okta widget. Providing the base URI is optional. |
   | Controlled access | Option to assign access to Okta integration in your organization. To assign access: * To assign access to everyone in the organization, select Allow everyone in your organization to access. * To assign access to selected groups, select Limit access to selected groups and enter the group names in the Selected group(s) field. * To assign access after integration, select Skip group assignment for now. {#conf-okta-app__ul_uqk_5hh_wyb} |
   [Tabela 1. New Web App Integration]

   {#conf-okta-app__table_jwz_52h_wyb}
8. Select Save.  
   The OAuth application is created.
9. Grant permissions to access Okta APIs.
   1. Select Okta API Scopes.  
   2. Under Actions, select Grant for the APIs.  
      Nota:  
      These are all the OAuth scopes required for all the spoke actions to work. If you are only using a subset of the available spoke actions, you can select only the scopes required, based on your own security requirements.
      * okta.users.manage
      * okta.apps.manage
      * okta.logs.read
      * okta.groups.read
      * okta.groups.manage
      * okta.users.read
      * okta.apps.read
      * okta.eventHooks.read
      * okta.eventHooks.manage

      {#conf-okta-app__ul_dnd_svh_wyb}For more information about the API scopes, see [Define allowed scopes](https://developer.okta.com/docs/guides/implement-oauth-for-okta/define-allowed-scopes/) in [Okta Developer Documentation](https://developer.okta.com/docs/).
   {#conf-okta-app__substeps_lzp_nvh_wyb}

### Create a connection record for Okta Spoke {#ariaid-title8}

Create a connection record that contains the information to connect to the Okta server. Your ServiceNow instance uses this form to send authentication requests to the OAuth application.

#### Antes de Iniciar

Importante:  
If you have configured different OAuth scopes as mentioned in step 9 of [Create an OAuth application in Okta](https://www.servicenow.com/docs/u~JI~zizFhqyagf~3v2EQQ#conf-okta-app "Create a custom OAuth application in your Okta developer's account to enable OAuth 2.0 authentication of the requests from your ServiceNow instance."), do not perform this procedure. Instead, perform the steps outlined in [Connect to a third-party OAuth provider](https://www.servicenow.com/docs/access?context=connect-3rd-party-oauth-provider&version=australia&pubname=australia-platform-security&ft:locale=en-US) and add the corresponding OAuth scopes that align with your Okta Web Application that are granted in step 9 of [Create an OAuth application in Okta](https://www.servicenow.com/docs/u~JI~zizFhqyagf~3v2EQQ#conf-okta-app "Create a custom OAuth application in your Okta developer's account to enable OAuth 2.0 authentication of the requests from your ServiceNow instance.").

Role required: admin.

#### Procedimento

1. Navigate to AllProcess AutomationWorkflow Studio.
2. Select the Integrations tab.
3. In the Search all connections field, enter <kbd class="ph userinput">Okta</kbd>.  
   Nota:  
   The Outbound tab is enabled by default. Confirm that it's enabled.
4. On the Okta spoke tile, select View Details.  
5. Select Configure.
6. On the form, fill these values.  
   {#add-okta-conn__table_fcw_r1h_3mb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the connection established with the Okta instance. The first connection's default name is automatically assigned to match the name specified in the Connections and Credentials form on the Connection \& Credential Aliases page. To provide your custom name, create a connection record by selecting Add Connection. |
   | Connection URL | The URL to connect to the Okta server. The URL format is https://\[yourOktaDomain\].com. |
   | API Version | The version of the Okta APIs. |
   | Authorization URL | The URL that the OAuth application at Okta provides to seek authorization to access the Okta resource server. The format is <kbd class="ph userinput">https://{youroktadomain}.com/oauth2/{API version}/authorize</kbd>. |
   | Token URL | The URL to obtain the access token. The format is <kbd class="ph userinput">https://{youroktadomain}.com/oauth2/{API version}/token</kbd>. |
   | Token Revocation URL | The URL provided by the OAuth authorization server that enables a client application to request the revocation or cancellation of access tokens and refresh tokens that were previously issued. The format is <kbd class="ph userinput">https://{youroktadomain}.com/oauth2/{API version}/revoke</kbd>. |
   | OAuth Client ID | The client ID generated in the Okta developer's account. |
   | OAuth Client Secret | The client secret generated in the Okta developer's account. |
   | OAuth Redirect URL | Redirect the URL to your ServiceNow instance. The format is <kbd class="ph userinput">https://{instance-name}.service-now.com/oauth_redirect.do</kbd>. |
   [Tabela 2. Configure Connection]

   {#add-okta-conn__table_fcw_r1h_3mb}
7. Select Configure and Get OAuth Token.  
   The OAuth Access token is generated for the Okta spoke.  
   Nota:  
   You must log in to Okta before the OAuth access token is granted.
{#add-okta-conn__steps_ftf_csq_gnb}