-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
PANIC: interface conversion: error is user.ErrUserProhibitLogin, not *user.ErrUserProhibitLogin #18561
Comments
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Feb 2, 2022
There was an unfortunate regression in go-gitea#17962 where following detection of the UserProhibitLogin error the err is cast to a pointer by mistake. This causes a panic due to an interface error. Fix go-gitea#18561 Signed-off-by: Andrew Thornton <[email protected]>
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Feb 2, 2022
Backport go-gitea#18562 There was an unfortunate regression in go-gitea#17962 where following detection of the UserProhibitLogin error the err is cast to a pointer by mistake. This causes a panic due to an interface error. Fix go-gitea#18561 Signed-off-by: Andrew Thornton <[email protected]>
Thank you for the logs - that makes fixing this very simple indeed. |
zeripath
added a commit
that referenced
this issue
Feb 3, 2022
There was an unfortunate regression in #17962 where following detection of the UserProhibitLogin error the err is cast to a pointer by mistake. This causes a panic due to an interface error. Fix #18561 Signed-off-by: Andrew Thornton <[email protected]>
lunny
pushed a commit
that referenced
this issue
Feb 3, 2022
Backport #18562 There was an unfortunate regression in #17962 where following detection of the UserProhibitLogin error the err is cast to a pointer by mistake. This causes a panic due to an interface error. Fix #18561 Signed-off-by: Andrew Thornton <[email protected]>
Chianina
pushed a commit
to Chianina/gitea
that referenced
this issue
Mar 28, 2022
There was an unfortunate regression in go-gitea#17962 where following detection of the UserProhibitLogin error the err is cast to a pointer by mistake. This causes a panic due to an interface error. Fix go-gitea#18561 Signed-off-by: Andrew Thornton <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Gitea Version
1.16.0
Git Version
No response
Operating System
Debian 11
How are you running Gitea?
Using Debian packages from here: https://gitlab.com/packaging/gitea
Database
PostgreSQL
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/9p4/0726fa74d36bfc617d9d8762cd1c1441
Description
When using an OpenID Connect provider and signing in, there is an error:
PANIC: interface conversion: error is user.ErrUserProhibitLogin, not *user.ErrUserProhibitLogin
My OpenID configuration (from DB):
{"Provider":"openidConnect","ClientID":"gitea","ClientSecret":"secret","OpenIDConnectAutoDiscoveryURL":"https://auth.example.com/.well-known/openid-configuration","CustomURLMapping":{},"IconURL":"","Scopes":["profile"],"RequiredClaimName":"roles","RequiredClaimValue":"gitea","GroupClaimName":"","AdminGroup":"gitea_admin","RestrictedGroup":""}
The user has an attribute called
roles
that has the following values:gitea
,gitea_admin
.On the frontend (with dev mode enabled), I get the following 500 error when clicking the OpenID login button:
could not find a matching session for this request
. I am using Keycloak as my OpenID provider.Everything is configured normally.
Screenshots
No response
The text was updated successfully, but these errors were encountered: