---
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


---

# OAuth Outbound

# OAuth Outbound {#ariaid-title1}

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

OAuth outbound enables you to pull data from a third-party provider to your
instance.

You must have the security_admin role to manage the OAuth integration.

You can configure outbound OAuth 2.0 for the following grant types:

* Connect to third-party provider: Use the client ID and secret to send it to the OAuth provider. For more information, see [Connect to a third-party OAuth provider](https://servicenow-prod.fluidtopics.net/~CI~S03mc2pqaDw4Bk3xxg "Configure how the client ID and secret are sent to your OAuth provider.").
* JWT Bearer: An authorization server validates a JWT token which enables identity and security information to be shared across security domains. For more information, see [Set up OAuth provider with JWT Bearer grant type](https://servicenow-prod.fluidtopics.net/XcSlmIyJ6eEDmjYvdTUbXQ#JWT-Bearer-token-support "JSON Web Tokens (JWTs) enable the capability to configure server-to-server API interactions between ServiceNow and external API providers without requiring any user intervention. This support enables Integration Hub or other automated tasks using JWTs to configure API and Service integrations with different providers.").
* SAML2 Bearer: Generates the SAML2 assertion and then exchanges the assertion for the access tokens wit the provider.  
  Hinweis:  
  For outbound request to SuccessFactors use the SAML2 Bearer as the Default Grant Type. To know more about how to configure SAML2 Bearer, refer the example in [Set up the v4.x.x](https://www.servicenow.com/docs/access?context=setup-successfactors&version=australia&pubname=australia-integrate-applications&ft:locale=en-US).
* Authorization code: The code that is granted to the client to obtain an access token, which is then used to obtain access to the resource. If you select this option, then you need an authorization URL (the URL of the authorization server).
* Resource owner password credentials: The user name and password of the user that is trying to obtain access to the resource.
* Client Credentials: The client ID and client secret, which are both used to get the access token. This method does not provide refresh tokens.
* MID Server: The MID Servers facilitate communication and data movement between a single ServiceNow® instance and external applications, data sources, and services. Use the Authorization code, resource owner password credential, SAML bearer, and JWT bearer OAuth grant types of OAuth for outbound integration requests through the MID Server. Personal Auth is also supported through the MID server.

{#oauth-outbound__ul_dg5_3zq_cxb}

You can configure OAuth provider scenario (Outbound): Your instance pulls data from a third-party provider.  
Hinweis:  
You must user authenticate for the first time to fetch the token post which, you don't need to authenticate using a user account before the token expiry.