The new CCX / Guest user license model mandates that users are registered in a secondary NAB / Domino directory.
This is easily achieved if we just create person documents but it is not sufficient if we look to entitle those CCX / Guest users for the best options of the new license model (entitlement for Nomad / nomad Web).
In order to support "Notes ID" based applications we need to be able to perform a real registration / maintenance of users.
Today the NotesRegistration (see https://help.hcltechsw.com/dom_designer/11.0.0/appdev/builds/H_NOTESREGISTRATION_CLASS.html ) has nothing that allows selection of the NAB where we want to store registered users.
We would like to be able to set the NAB / Server name for the registration so that:
Person documents are created in the right place
Notes IDs are created and stored in vaults accordingly to policies
Public key for the Notes ID is stored and maintained in the right person document in the secondary NAB used for CCX/Guest users
This would be a perfect addition for Domino 12.0.1 (or even an intermediate fixpack)
Today we have "RegistrationServer" property. We would like to have an additional "RegistrationAddressBook" option to set the target NAB
[Daniele Vistalli / Factor-y S.r.l.]
I have another use case.
One of our customers provides web-based Notes-Applications with self registration (in some cases with confirmation workflow). Those registered users will be added to an additional Directory which has been added to Domino via DA.
We would like to offer those users a way of using MFA. This would of course make it necessary to be able to register those users in the "secondary" directory.
So, here's my vote.
thanks for the clarification. The request makes sense IMHO regardless of this. Now that IDVault is the way to go (and maybe CA Process too). I think that creating uses in ‘non primary’ address book gets even more complicated. Otherwise we will continue to work with hacks when we need/want to segregate users.
Maybe lower priority but still makes sense IMHO
the CCX/Guest model does not mandate to register users in a secondary NAB. It is just a rather common approach customers have used in the past where e.g. self registrations are put into a secondary directory. You dont have to do that.