OAuth Inbound and Outbound authentication

  • 릴리스 버전: Australia
  • 업데이트 날짜 2026년 03월 12일
  • 소요 시간: 3분

    • OAuth based authentication validates the identity of the client that attempts to establish a trust on the system by using an authentication protocol.

    OAuth 2.0 - Open Authorization is the industry-standard protocol for authorization, that ocuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, and mobile devices.

    It is a standard that is designed to allow a website or application to access resources hosted by other web apps on behalf of a user.

    Instead of using the resource user's credentials to access protected resources, the client obtains an access token. Access tokens are issued to third-party clients with the user's approval, the client then uses the access token to access the protected resources.

    From Zurich, you can configure OAuth integration with the following enhancements:

    • Increase client secret length to 2048 characters to meet security requirements of third-party systems like Azure DevOps (ADO).
    • Provide a JSON Web Key Set (JWKS) URL to automatically manage and update the public key for JSON Web Tokens (JWT) signature validation.
    • Request OAuth tokens using the JWT grant type signed with Enhanced Security (ES) algorithms.
    • Configure a unique identifier for JWT tokens.

    Inbound

    Create an endpoint for external clients that want to access your instance. This creates an OAuth client application record and generates a client ID and client secret that the client needs to access the restricted resources on the instance. For more information see, OAuth Inbound.

    Outbound

    Use a third-party OAuth provider that provides the authorization for access to your instance. Specify an OAuth profile and OAuth scope when you are connecting to another OAuth provider. For more information see, OAuth Outbound.