-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Missing SSH public keys from LDAP #14849
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
Comments
Sorry, I was misleaded by the need to logout/login again to see changes done in LDAP. Sounds like a revival of #13984 but I cannot find traces of the fix for that one in the CHANGELOG.md file. @zeripath any idea bout that ? Could you figure that out and add to CHANGELOG in the appropriate section ? |
Logs from Gitea, about the "common substring":
|
Another problem (needs another ticket?) is that even if I enter a single key, |
Gitea Version: 1.12.3 <- do you mean 1.13.2 or 1.12.3? |
#13989 and #14607 are not in a released version of Gitea yet and they won't go in to 1.12. #14607 will be in 1.13.3 when it is released. Please re-test on release/v1.13 or master. I'm closing as duplicate please reopen if this remains true on release/v1.13 or v1.13.3 when it is released. Duplicate #13984 |
I'm still having trouble with public ssh keys synchronization from LDAP.
I have added 4 sshPublicKey in LDAP but only see 2 in Gitea.
One thing I noticed is that 3 of those 4 keys I have in LDAP all start with the same list of characters, and the portion of the key shown by Gitea is the start of such "common substring". Maybe Gitea is just assuming the keys are EQUAL due to this shared initial string ? The keys are of ecdsa-sha2-nistp521 type and the first character outside the substring shown by Gitea is a
b
(not found before).It would help if Gitea showed the whole key somehow, or at least the key comment at the end, to know what it's taking in consideration.
Gitea Version: 1.12.3
The text was updated successfully, but these errors were encountered: