---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# User Token Flow

# Third party token workflow for user accounts {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 30. Juni 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

This workflow can be used to integrate third-party identity providers (IdPs) with ServiceNow® for secure API access. It allows client applications to obtain tokens directly from an IdP and use them to access ServiceNow APIs.

## Vorbereitungen

Role required: <kbd class="ph userinput">oauth_admin, mi_admin, admin</kbd>

## Warum und wann dieser Vorgang ausgeführt wird

The third-party client application requests tokens directly from your identity provider (IdP). The authentication method between the client and the IdP is flexible and can be configured to meet your specific requirements. After successful authentication, the IdP issues an ID token or access token, and optionally a refresh token. These tokens are sent directly to the client application, which then uses them to access ServiceNow APIs.  
Hinweis:  
ServiceNow validates the token using the public key configured during setup and grants access to the requested APIs. Ensure that the token is in JSON Web Token (JWT) format.
Abbildung : 1. User Account Workflow

## Prozedur

1. Configure your third party client application.  
   Set up your third party client application to request tokens directly from your identity provider (IdP). Select an authentication method that best fits your security and integration requirements.
2. Create an OAuth client in ServiceNow.  
   Provide the required details to enable validation of incoming tokens from your identity provider (IdP).