---
sourceDocument: Australia Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-security

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Configure push notification (Okta Verify)

# Configure push notification (Okta Verify) {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure Okta Verify to receive push notifications for secure and convenient identity verification.{#configure-okta-verify-push-notification__patch-rn-zp4-1}

## Before you begin

Role required: auth_factors_admin

The push notification authentication factor on Okta must be enabled. To learn more, see [Okta Support Center](https://support.okta.com/help/s/article/Enable-Okta-Verify-Push-Notification-in-OIE?language=en_US).  
Note:  
* Currently, only Okta Verify is supported for push notifications with ServiceNow AI voice agents.
* The users must have the Okta Verify app installed and configured on their phones.
{#configure-okta-verify-push-notification__ul_pwd_wjz_mhc}

## Procedure

1. Log in to your Okta admin account.
2. Navigate to SecurityAPI.
3. Select Tokens.  
   Figure 1. Okta Admin Console
4. Select Create token to create token and copy its value.  
   For example, `O0EYJEm|b34aYViOYaav3KnqxsItV_mPI9_p2N46Cc`.  
   Note:  
   Create the token from a dedicated service account that has only the permissions push needs. A token has the same privileges as the admin who creates it, expires after 30 days without use, and stops working if that admin account is deactivated. If push goes unused for 30 days, create a new token.
5. On the instance, open the Connection \& Credential Alias record.  
   For example, `<instance_url>/sys_alias.do?sys_id=692e16a0ffb72210d487ffffffffff1b`.
   Figure 2. Connection \& Credential Alias new record
6. Select New under the Connections tab.
7. Specify the following field on the HTTP(s) Connections form.  
   * Name
   * Connection alias
   * Connection URL

   {#configure-okta-verify-push-notification__ul_rhk_xfr_hhc} Figure 3. HTTP(s) Connections details
8. Select the Search icon next to Credentials to add new API Key Credentials.  
   Figure 4. API Key Credentials selection
9. Specify the Name and API Key on the API Key Credentials form.  
   Note:  
   The API key should be prefixed with 'SSWS'. If the copied token value is <kbd class="ph userinput">00iJ88ydm9ZLnDNE8AeGsmjcUC-ZFyCt3pts2pNTwZ</kbd> you must provide the value as <kbd class="ph userinput">SSWS 00iJ88ydm9ZLnDNE8AeGsmjcUC-ZFyCt3pts2pNTwZ</kbd>.
   Figure 5. API Key Credential details
10. Select Submit to submit the API Key Credentials.
11. Select Submit on the Connection record.  
    Figure 6. HTTP(s) Connections record completion

*[\>]: and then