-
Notifications
You must be signed in to change notification settings - Fork 4.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
LDAP handshake failure from version 2.11 #20691
Comments
The same issue. |
What's your AD? And the version of your AD? |
Any idea where to put that to make it persistent ? If I run the harbor |
@stonezdj thanks for that workaround. I confirm it works with that set. I had some trouble understanding the issue @wy65701436 pointed out. Does it says that now tls 1.2 support is disabled by default on the golibrary used to perform the connection? @vaz-ar I can't answer yours, because I am using harbor via a helm installation. So in my case I edited the values files adding it to the "extraEnvVars" field under core. |
Golang 1.22 still supports tls 1.2, but it removed some weak TLS cipher suites that start with TLS_RSA_*. |
You should manually update the env file after run |
Thanks for explaining it to me. That being the case, I am ok with closing this issue |
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
Starting on version 2.11 I can't connect to ldaps, it works with the exact same configuration on version 2.10.2
Expected behavior and actual behavior:
Failed to verify LDAP server with error: error: ldap server network timeout.
and the core logs report:Steps to reproduce the problem:
Upgrade harbor from 2.10.2 to 2.11.0, and configure LDAP auth
Versions:
Please specify the versions of following systems.
The text was updated successfully, but these errors were encountered: