2. The user accesses the Web site and applies for new registration and submits the form.
3. The application admin receives the submitted form and clicks the create ID button to create the person document in a secondary address book.
4. After creating the IDs, the Lotus script will add the ID to a ?group? in the primary address book, which is a member of ?main group? in the primary address book.
5. The Application contains the main group in the ACL with appropriate access level assigned (author with some roles). The problem is after the create ID button is triggered, the ID creation has an immediate effect, but the database ACL doesn't take effect immediately. This means that after the IDs are created, the Web user is able to use the ID to logon from the Web site but unable to access the database even though the ID is a member of subgroup. The message reads: "you are not authorized to open the database". Note: The above problem doesn't appear when we use our development server (5.08) but the problem persists when we installed it in the production server.
It probably has to do with group access being cached by the server. The indexer isn't refreshing the $Groups view, the $ServerAccess view, etc., immediately. That?s why you have your delay.
Dig Deeper on Domino Resources - Part 6
Related Q&A from Michael Lazar
Learn how to easily keep track of the numbers of incoming and outgoing Lotus Notes email messages to and from your Domino server each day. Continue Reading
Discover what steps you can take if your Lotus Domino server runs out of disk space and you have issues sending and receiving Lotus Notes email ... Continue Reading