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
Right now this service expects from us Authorization: Basic, which is not so bad from CURL perspective - just -u "username:token", but that still requires from us to know a GH user behind provided token.
The GithubAuthenticationManager can be adjusted to just rely on that provided GH token and then probably call respective GH API: https://docs.github.com/en/rest/users/users?apiVersion=2022-11-28#get-the-authenticated-user.
This would let our project-api clients to avoid extra gh api /user --jq '.login' call or hard code username into our clients or require it alongside with the token.
The text was updated successfully, but these errors were encountered:
Right now this service expects from us
Authorization: Basic
, which is not so bad fromCURL
perspective - just-u "username:token"
, but that still requires from us to know a GH user behind provided token.The
GithubAuthenticationManager
can be adjusted to just rely on that provided GH token and then probably call respective GH API: https://docs.github.com/en/rest/users/users?apiVersion=2022-11-28#get-the-authenticated-user.This would let our
project-api
clients to avoid extragh api /user --jq '.login'
call or hard codeusername
into our clients or require it alongside with thetoken
.The text was updated successfully, but these errors were encountered: