-
-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Authorization Bearer header instead of PAT on demand #877
Comments
Interesting. I'm trying to play around with oath2 but :( sadly cannot figure a valid URI on gitlab. Let me try a few things to see if I can get some test code to you. |
@mfriedenhagen, can you try the following quick hack and let me know if this works?
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
api
as well.git
operations likepull
orpush
.lab
. However I get a 401 when setting the oauth bearer token asLAB_CORE_TOKEN
.lab
does use the headerPRIVATE-TOKEN
which does only accept a GitLab PAT.curl and use the oauth token as bearer token in the
Authorization` header, this does succeed.[a-f0-9]{64}
so it should be quite easy to differentiate a PAT and this kind of token.The text was updated successfully, but these errors were encountered: