#dominoforever | Product Ideas Portal

 

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Domino dirsync is expected to be able to pick the CN with a comma in between the first name the last name from the distinguished LDAP DN and should not consider this as a name change comparing it to the Domino User Name on sync.

As currently if there is a "comma" or a "Backslash" between the first name and second name in the CN of the LDAP DN, then the dirsync when compares it with the Domino Name raised a name change request and gets it processed as well which is inappropriate.

And the only possible way to fix it is that from the remote LDAP end the CN in the LDAP DN should not have such character such as comma & Backslash.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 23 2020
  • Needs review
  • Attach files