-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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 "slice bounds out of range" with LDAP SSH keys #5975
Comments
|
Pretty sure the issue is that the LDAP result is |
yup that looks like that would be the problem... |
OK I've put a PR up. I wasn't sure if you were wanting to do this. If you can, could you test to see if there's another bug that this is being hidden by this one? |
No problem, I had the exact same fix in mind, but wanted to test it before sending a PR. Deployed the fix now and the user was able to login, thanks! |
I have a LDAP auth source and a user that has no SSH public keys on LDAP. When I add the attribute 'sshPublicKey' to the authentication source, the user can no longer log in on the web interface and the following panic is logged in
gitea.log
. If I remove the LDAP attribute, the user is again able to log in. I assume that case of emptysshPublicKey
result may not be handled properly arounduser.go:1504
.The text was updated successfully, but these errors were encountered: