You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The token scopes for the Gitlab provider are hard-coded in the source code: read_repository & write_repository.
I would like to use the token, created by GCM, also for Maven dependency resolution via the package registry API (in a Gradle Kotlin Script).
This is only possible if you request a token with the scopes "api" or "read_api".
Unfortunately the gitlab provider does not allow to override the scopes with the credential.oauthScopes property, defined by GCM.
The Scope parameter is read by GCM (TryGet "oauthScopes"), but not used when requesting the token. Therefore the token can only be used to perform Git operations.
The text was updated successfully, but these errors were encountered:
Feature description
The token scopes for the Gitlab provider are hard-coded in the source code: read_repository & write_repository.
I would like to use the token, created by GCM, also for Maven dependency resolution via the package registry API (in a Gradle Kotlin Script).
This is only possible if you request a token with the scopes "api" or "read_api".
Unfortunately the gitlab provider does not allow to override the scopes with the
credential.oauthScopes
property, defined by GCM.The Scope parameter is read by GCM (TryGet "oauthScopes"), but not used when requesting the token. Therefore the token can only be used to perform Git operations.
The text was updated successfully, but these errors were encountered: