Open pierreedbrg opened 1 year ago
If there is a security vulnerability, it is to the admins to mitigate the risks, disabling a main feature of ldap bind is a breaking changes as it's expected to be working since it's an ldap feature used in every services. Moreover, it all depends of the exposure of your harbor instance, if it's not publicly exposed, the risk is highly reduced.
To summarize, even though there is a vulnerability, it is more in the configuration of ldap than from the connection itself. if we accept this risk, then it's our responsability.
Is it not possible in the latest version of harbor to bind to ldap using anonymous bind, which is a problem as you must set the hardcoded password in every applications.
Is it possible to enable anonymous bind as for example gitlab enables anonymous bind for synchronization ?
it forces us to create a ldap user with readonly permission with a password that has no point. Moreover it is a pain to manage as if the password changes, you have to manually change it in every app.
Thanks.