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
This is an idea that came up around AdminCentral for Domino V14, too.
But it is a bit problematic from security point of view.
Adding a user to the same groups is probably OK from security point of view.
But having a function to go thru all ACLs and add the user in the same way is problematic from security point of view.
Having a list of groups an existing user is in could be presented to an admin before registration of a new user. That should be perfectly OK from security point of view. The admin would see if there are some special groups that the other user might not be intended to be in.
But explicit ACL entries are a different animal. You can't just add the user exactly the same.
So imagine another user granded access rights explicitly for this reference user.
Would you really add the new user with access to that other users mailfile?
This is just one example. But there could be many others cases where you don't want all ACL entries to be exactly the same.
I would see groups reference as a very good idea. But I would vote no for all ACL entries!
Usually access should be granted by groups. If there is an explicit ACL setting, this looks more like a special permission.
If an environment does not use groups for access, the process of how permissions are assigned to users should be reviewed IMHO.
[ Daniel Nashed / https://blog.nashcom.de ]