Chapter 1. Introduction to Red Hat Quay OAuth 2.0 tokens
OAuth 2.0 tokens provide secure, standards-based access to the Red Hat Quay API. You can use OAuth 2 access tokens, robot account tokens, and OCI referrers access tokens to authenticate API operations.
Compared to more traditional API tokens, Red Hat Quay OAuth 2 tokens offer the following enhancements:
- Standards-based security that adheres to the OAuth 2.0 protocol.
- Revocable access by deleting the application in which the OAuth 2 token exists.
- Fine-grained access control so that Red Hat Quay administrators can assign specific permissions to tokens.
- Delegated access so that third-party applications and services can act on behalf of a user.
- Compatibility with other services, platforms, and integrations.
Red Hat Quay primarily supports two types of tokens: OAuth 2 access tokens and robot account tokens. A third token type, an OCI referrers access token, that is required to list OCI referrers of a manifest under a repository, is also available when warranted.
You can manage organization OAuth 2 access tokens from the API Access Tokens page of an OAuth application. You can create named tokens with optional expiration, review metadata such as scopes and last-used time, and revoke individual tokens without deleting the parent application.