Web Authentication of users created by Registration DB failing?!?

HCL Domino Domino Forum
1

Please help! Any ideas would be greatly appreciated by this relatively new Notes developer.

I am working on a web shopping cart and everything has been going fairly smooth until yesterday. In the middle of working on the app, the group assigned for Web Authentication failed to authentication.

For restricted forms I used a check only in the box for a group called DownloadGlobalUsers in the options for “Who can create documents for this form”.

DownloadGlobalUsers is a group created by an Agent in the Web Registration database from IBM. This has worked fine for several weeks, until yesterday. I can change the access from DownloadGlobalUsers to another group that the webuser has access to and it works. But for some reason authentication is not recognizing the group being created by the agent any longer. As far as I can tell, the Agent Created group and other groups that work seem identical in the NAB. Their settings are all the same.

I changed the agent to create a new group name (Restricted Web Access), deleted all of the web accounts from the NAB, restarted the server and started over with the new group name. Same thing.

As far as I know, no settings changed when it stopped working but I have spent the last two days looking over all of the settings for something that could be causing this. To no avail.

Any ideas???

2

Subject: How many names are in the group?

3

Subject: How many names are in the group?

When then authentication for that group failed there were three or four groups in it.

The way the agent creates the group is making it a subgroup of the main group. The main group is DownloadGlobalUsers, then the agent creates a sub-group called DownloadGlobalAgents1. Within the subgroup there were three agent created users.

I have tried using the Main group, the sub-group, and both groups for authenticating. None work.

*** Also, if I add a user explecitly to the ACL it works. Then after I remove the user from the ACL it still continues to work. It seems like implicit authentication doesn’t work until after a user is explecitly put in the ACL.