OAuth compliant authorization header #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Using
PRIVATE-TOKENheader users can only use personal/project/group tokens, and can't use OAuth tokens.Solution
According to gitlab documentation https://docs.gitlab.com/ee/api/rest/#personalprojectgroup-access-tokens there's also OAuth compliant way to authorize which works with personal/project/group and OAuth tokens.
Checks