HCL Domino 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
Certificates are not in question, only the field that is used during the creation of it.
Why not create a hash when you create a user and that has is used for generating the certificate?
Now UserName is used and that is sooo inefficient. UserName is the key, and is changed often. This is calling out for soo much problems.
The reason for the problems is that there are organizations that are not allowed to change the owner of a mail or calendar information. You wrote a mail or invited someone with your old name, not with your new name. It's now allowed because you cannot alter this kind of information. We have disable this in mail and certain databases.
When you take a look at Outlook/Exchange/AD, users are registered with a GUID ( Like HCL Connections ), and this one is the hash that is not changed. You can easily change the name of the user without running complex renames in names/reader fields. Sometimes ADMINP lost track of the renames and people are not renames correctly. And the rename takes a while in Domino, when you have 80 servers....it takes almost 3 weeks.
So, still use certificates but based on a hash and not the username so we can rename users without long running renames processes in ADMINP.
Our entire system is based on certificates and certificates are issued for an identity, so how can one validate the identity if all you have is a hash that can map to any form of username string?