You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually, LDAP clients support specifying bind- and base-DN-s eparately, because not everyone wants to give all the users access to reading the LDAP database. (E.g. the binding mechanism might happen entirely on the application side, but clients pass their credentials to authenticate.)
Our LDAP access is also configured so that we can only bind with admin.
So at the moment, at least based on my interpretation of the config and docs, we can only authenticate with the admin user.
The text was updated successfully, but these errors were encountered:
Usually, LDAP clients support specifying bind- and base-DN-s eparately, because not everyone wants to give all the users access to reading the LDAP database. (E.g. the binding mechanism might happen entirely on the application side, but clients pass their credentials to authenticate.)
Our LDAP access is also configured so that we can only bind with admin.
So at the moment, at least based on my interpretation of the config and docs, we can only authenticate with the admin user.
The text was updated successfully, but these errors were encountered: