-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Support for Oauth in API #3033
Comments
If this was supported, then https://github.com/google/go-github would work with gogs by just overriding the |
Gogs had OAuth-support a while back but was removed since no-one wanted to maintain it. And no, google/go-github wouldn't work since Gogs has a slightly different json-schema 😞 |
@bkcsoft is there a link to the old commit for oauth2 that was working? there might be some someone interested in looking at or maintaining oauth2. I want to point them to the right resources. also @unknwon what was wrong with the previous oauth2 implementation? what mistakes would a new maintainer have to avoid to get oauth2 added? |
Anyone looking for this feature may benefit from reading these two issues: |
@stevegt thanks for the comment! go-gitea has login/authn oauth2, and commit status apis just merged. I think once you can generate scoped oauth2 tokens that can have read only access to the repo and update commit status, go-gitea would integrate with drone in a similar way that drone integrates with github or bitbucket. exciting! |
Authentication tokens cannot be passed using standard OAuth2.
The following code returns a 401 HTTP error, but passes by adding
?token=<mytoken>
to the URL:The text was updated successfully, but these errors were encountered: