Document URL: https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/configuring-special-binds#unauthenticated-binds Section Number and Name: 15.7.3. Allowing Unauthenticated Binds Describe the issue / Suggestions for improvement: * "changetype: replace" must be "changetype: modify" * In the "ldapsearch" example, it's not obvious that we don't enter a password when we use -W. It would be better to use -w "" instead. * Add a <warning> that this dangerous!
> Unauthenticated binds only apply to bind attempts where a password is > not given but a bind identity is. This also doesn't seem to be correct. In my 10.1 test environment I can connect without or with an non-existent user name and get results. For example: # ldapsearch -D "cn=non-existent-user" -w "" -p 389 -h server.example.com -b "dc=example,dc=com" -x
The parameter description in the Configuration, Command, and File Reference needs a huge <warning>, too.
The update is now available on the Customer Portal.