Commit c28800c2 authored by Mike Jang's avatar Mike Jang Committed by Nick Gaskill

Add section describing OAuth2 token use in registries

parent bf1611e8
...@@ -354,3 +354,13 @@ These are aliases for `scope` and `expires_in` respectively, and have been inclu ...@@ -354,3 +354,13 @@ These are aliases for `scope` and `expires_in` respectively, and have been inclu
prevent breaking changes introduced in [doorkeeper 5.0.2](https://github.com/doorkeeper-gem/doorkeeper/wiki/Migration-from-old-versions#from-4x-to-5x). prevent breaking changes introduced in [doorkeeper 5.0.2](https://github.com/doorkeeper-gem/doorkeeper/wiki/Migration-from-old-versions#from-4x-to-5x).
Don't rely on these fields as they will be removed in a later release. Don't rely on these fields as they will be removed in a later release.
## OAuth2 tokens and GitLab registries
Standard OAuth2 tokens support different degrees of access to GitLab registries, as they:
- Do not allow users to authenticate to:
- The GitLab [Container registry](../user/packages/container_registry/index.md#authenticate-with-the-container-registry).
- Packages listed in the GitLab [Package registry](../user/packages/package_registry/index.md).
- Allow users to get, list, and delete registries through
the [Container registry API](container_registry.md).
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment