-
-
Notifications
You must be signed in to change notification settings - Fork 385
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
Error while authenticating against OAuth provider #4450
Comments
I tested exactly this version yesterday and didn't have that error. |
Which configs do you need for Gitea? Gitea version: 1.23.0+dev-704-g633785a5f3
Woodpecker logs::
Woodpecker environment variables:
|
Did it work on |
Alright. I have found a way to check if a previous nightly works. This version is based on this commit go-gitea/gitea@a175f98 which is the last commit before the PR I think is causing the issue. Hope this helps. |
I am also using woodpecker, and I also encountered the problem. Will be fixed by Improve oauth2 scope token handling go-gitea/gitea#32633 Feel free to try my fix. |
I just tried your fix and it works. |
With go-gitea/gitea#32633 being merged this issue is now resolved I think. |
Component
server
Describe the bug
I am aware that I run both Gitea and Woodpecker at the edge by using
nightly
andnext
versions and that this can cause issues.When trying to access Woodpecker I am send to the login page.
After trying to login I get the following error message: "Error while authenticating against OAuth provider"
I think this has to do with a recent PR being merged in Gitea about granular scopes.
The error messages Woodpecker returns are about a token not having at least one required scope.
In a attempt to fix the issue I had revoked Woodpecker as an "Authorized OAuth2 Application" in Gitea.
Re-adding does not fix the issue.
Steps to reproduce
Expected behavior
No response
System Info
Additional context
Woodpecker logs:
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: