Revoking Refresh Tokens

Note: This documentation assumes you have read the basic SSO flow and that you understand what a refresh token is used for.

If you know your refresh token has been compromised, it is important to revoke it. This documentation will show you have to do that and you can read RFC 7009 if you want to dig into even more details.

  1. Find EVE SSO’s revocation endpoint by making a GET request to its meta route which can be found at URL You will get a response similar to this:

         "issuer": "",
         "authorization_endpoint": "",
         "token_endpoint": "",
         "response_types_supported": [
         "jwks_uri": "",
         "revocation_endpoint": "",
         "revocation_endpoint_auth_methods_supported": [
         "token_endpoint_auth_methods_supported": [
         "token_endpoint_auth_signing_alg_values_supported": ["HS256"],
         "code_challenge_methods_supported": ["S256"]

    From here you want to get the value of the key revocation_endpoint, which at this time of writing is

  2. Make a POST request to the revocation endpoint retrieved from step 1 using basic authentication, where your application’s client ID is the user and your application’s secret key is the password, with the form encoded body:

     token_type_hint=refresh_token&token=<your refresh token to revoke>

    Replace all text wrapped with <> with a value provided by you.

    Make sure to set the correct Content-Type header:

     Content-Type: application/x-www-form-urlencoded
  3. The server responds with a 200 OK response code. If you submitted a valid token, the server has now invalidated it. Note that the server also returns a 200 OK if the token was invalid, because in both cases the end result is the same - you are not able to use the token to successfully request a new access token.

If you’d like to look at an example of revoking a refresh token written in Python you can find one here.