Yandex Cloud
Documentation
PresentationContact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.
Yandex Identity and Access Management
    • All guides
    • Getting information about subjects
    • Processing secrets that have become publicly available
    • Users
    • User groups
      • Overview
        • Overview
        • Getting a list of refresh tokens
        • Revoking a refresh token
      • Managing static access keys
      • Managing API keys
      • Managing authorized keys
      • Creating a temporary access key using Security Token Service
      • Managing ephemeral access keys
  • Secure use of Yandex Cloud
  • Access management
  • Pricing policy
  • Role reference
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  1. Step-by-step guides
  2. Authentication
  3. Refresh tokens
  4. Revoking a refresh token

Revoking a refresh token

Written by
Yandex Cloud
Updated at November 17, 2026
View in Markdown

Note

Once issued in the application, refresh tokens are automatically added to the user profile.

To revoke a refresh token for a federated or local user:

Cloud Center UI
CLI
API
  1. Log in to Yandex Identity Hub using an administrator or organization owner account.
  2. In the left-hand panel, click Users.
  3. Locate the user in the list. Use the filter or search bar at the top of the screen as needed.
  4. Navigate to the Refresh tokens tab.
  5. Click next to the token and select Delete.
  6. To revoke all tokens, click Delete all tokens.

You can also revoke your refresh tokens through the My account portal. This feature is also available to Yandex account users.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

  1. View the description of the command for revoking a refresh token:

    yc iam refresh-token revoke --help
    
  2. To revoke certain refresh tokens, get their IDs first.

  3. To revoke one or multiple refresh tokens for a user, run this command:

    Warning

    You can run the yc iam refresh-token revoke command without any additional settings. In this case, it will revoke all refresh tokens for the user currently authenticated in the Yandex Cloud CLI.

    When revoking all refresh tokens for the current user, the yc iam refresh-token revoke command will first prompt you to confirm this action in the terminal.

    yc iam refresh-token revoke \
      --refresh-token <refresh_token_body_in_stdin>
      --refresh-token-id <refresh_token_ID> \
      --subject-id <user_ID> \
      --client-id <OAuth_app_ID> \
      --client-instance-info <OAuth_app_version>
    

    Where:

    • --refresh-token: Body of the refresh token to revoke. Provide the value in the standard input stream, stdin. This is an optional setting. Here are examples of use:

      • To provide the token body in a string: yc iam refresh-token revoke --refresh-token <<< "<refresh_token_body>".
      • To provide the token body in a file: yc iam refresh-token revoke --refresh-token < <path_to_refresh_token_body_file>.

      You cannot use any other yc iam refresh-token revoke settings together with --refresh-token.

    • --refresh-token-id: ID of the refresh token to revoke. This is an optional setting.

      You cannot use any other yc iam refresh-token revoke settings together with --refresh-token-id.

    • --subject-id: ID of the federated or local user whose refresh tokens you want to revoke. This is an optional setting. If you skip it, the system will revoke the refresh tokens for the user currently authenticated in the Yandex Cloud CLI.

      By default, any federated or local user can revoke their refresh tokens. To revoke refresh tokens for other users, a user needs one of the following roles for the organization: organization-manager.federations.userAdmin or iam.userAccounts.refreshTokenRevoker.

    • --client-id: ID of the OAuth application you want to revoke refresh tokens for, e.g., yc.oauth.public-sdk for the Yandex Cloud CLI. This is an optional setting.

    • --client-instance-info: Version ID of the OAuth application you want to revoke refresh tokens for. Here is an example: yc/0.141.0. This is an optional setting.

    Result:

    done (3s)
    refresh_token_ids:
      - dda5243b-34b9-415e-a534-fdb8********
      - 07998b66-9f3d-472b-9357-a904********
    

Use the revoke REST API method for the RefreshToken resource or the RefreshTokenService/Revoke gRPC API call.

Refresh tokens are also automatically deleted seven days after their lifetime expires.

Was the article helpful?

Previous
Getting a list of refresh tokens
Next
Managing static access keys
© 2026 Direct Cursus Technology L.L.C.