Configure Back-Channel Logout

Configure Back-Channel Logout

Before you start

To use back-channel logout, your application must meet the following requirements:

  • Your logout callback endpoint must be exposed over the internet for your Auth0 tenant to access.

  • Production-ready applications must use TLS.

  • The application must be able to store the provided session identifier (sid) and associate it with the user sessions it creates. We recommend production applications use durable session storage.

  • The application must be able to retrieve an existing session by the sid during the logout process without using client-side cookies. Cookies exist within the browser and are inaccessible to the logout callback endpoint.

Verify availability

Check the OIDC standard /.well-known/* metadata endpoint to determine if the service is available for your application. This is a read-only public endpoint.


HTTP 200
{ ..., "backchannel_logout_supported": true, 
  "backchannel_logout_session_supported": true }

Was this helpful?


Back-Channel Logout restrictions

Callback URLs are called on publicly-exposed endpoints and must adhere to certain restrictions:

  1. You must use the HTTPS protocol. Unencrypted HTTP or any other protocols are not allowed.

  2. You must not use Auth0 subdomains. Some Auth0 subdomains are:





  3. We do not recommend using IP addresses without domains. IP addresses must be public IPs to use back-channel logout. IP addresses from internal, reserved, or loopback ranges are not permitted.

Configure Auth0

Register your application to receive back-channel logout events in Auth0 Dashboard or Management API.

Subscribe applications

  1. Navigate to Auth0 Dashboard > Applications.

  2. Choose the application you want to register.

  3. Select the Settings tab.

  4. Under the OpenID Connect Back-Channel Logout > Back-Channel Logout URI, add the application logout URI that will receive the logout_tokens

  5. Once complete, select Save Changes.

    Auth0 Dashboard > Applications > Settings > Sessions tab

Unsubscribe applications

Unsubscribing your application stops the service from tracking new logins and sending logout events. The service discards pending logout events once your application is unsubscribed.

To unsubscribe your application, delete the back-channel logout URL.

  1. Navigate to Auth0 Dashboard > Applications.

  2. Choose the application you want to register.

  3. Select the Settings tab.

  4. Under the OpenID Connect Back-Channel Logout > Back-Channel Logout URI

  5. Remove the back-channel URL.

  6. Once complete, select Save Changes.

    Auth0 Dashboard > Applications > Settings > Sessions tab

For auditing purposes, the service always logs subscribing or unsubscribing back-channel logout URLs as API Operation Event in Auth0 tenant logs. To learn more, read Logs.

Auth0 Dashboard > Monitoring > Logs

Configure your application

Once you have configured back-channel logout via the Auth0 Dashboard or Management API, configure your application to use the service based on the technology or framework.

  1. Implement end-user authentication according to your application type. 

    1. End-users should be able to log in to the application, and a session should be created. 

    2. An ID token should be issued from Auth0 and should be accessible in the application backend for further processing.

  2. Extend the login process to save the sid and, optionally, sub claims after the ID token is validated. 

    1. These claims must be saved against the current application session. 

    2. The session management functions should be able to retrieve a specific session by the sid value.

  3. Configure the logout callback endpoint:

    1. The endpoint must process only HTTP POST requests.

    2. Extract the logout_token parameter and validate it as a regular JWT according to the spec.

    3. Verify that the token contains an events claim with a JSON object value and a member named

    4. Verify that the token contains the sid and/or sub claims.

    5. Verify that the token does NOT contain the nonce claim. This is required to prevent abuse by distinguishing the logout token from the ID token.

    6. Once the token is validated, retrieve the session corresponding to the received sid and/or sub value and terminate it. The exact application session termination process depends on the implementation details. For example, this event may need to be communicated to the front-end.

Logout callback example

Coded token payload:

POST /backchannel-logout HTTP/1.1
Content-Type: application/x-www-form-urlencoded


Was this helpful?


Decoded token payload:

  "iss": "",
  "sub": "google-oauth2|113812989461878752311",
  "aud": "45DXmtNEeUdMqz4tpVAvYPlQEbnMdZlE",
  "iat": 1663931440,
  "jti": "951de5a3-bdc7-4210-a34c-8ef2495f59e0",
  "events": {
    "": {}
  "trace_id": "74f2d5cb9b71d0d9",
  "sid": "xNvDYnS6tzcP6ZUn9wjPfY1IhfCIamgY"

Was this helpful?


Expected responses

  • HTTP 200:  Confirms user logout from the specific application.

  • HTTP 400: Indicates an incorrect request. The request is not understood or the token failed validation. Auth0 records the problem in tenant logs but does not attempt further requests for this specific session.

Troubleshoot issues

Application did not receive the logout events

If your application did not trigger logout and received a 400 error:

  1. Make sure your application has a logout callback URL registered in Auth0 Dashboard.

  2. Ensure the logout callback URL is reachable from the Auth0 tenant.

  3. Ensure a valid session is established. The end-user must log in to your specific application via Auth0.

  4. Check Auth0 tenant logs for messages about unsuccessful logout message delivery. Failed deliveries are not retried.

    Auth0 Dashboard > Monitoring > Logs

  5. Make sure the logout is triggered via the standard logout endpoint. Other events do not trigger the logout events.

  6. If possible, check for blocked requests on the web server and/or application firewall logs.

Client app cannot verify the received logout token

If the transaction still fails with a 400 error:

  1. Check if the token is a standard base64-encoded JWT. Some web servers may truncate long parameters. To learn more, read Signing Algorithms.

  2. If possible, capture a token and verify that it’s a JWT. Use a verified source, like JWT.IO.

  3. Make sure the verification function fetches the tenant signing key dynamically via JSON Web Key Sets (JWKS).

Was this article helpful?