Trust Signer keeps popping up for one user
I created a database in Notes that basically has a purpose to track projects. When I let the users use it, it gave them a pop-up about trusting the signer, but once they choose to trust the signer they don't get that pop up anymore.
Now, one user always get that pop-up when he tried to create a project, even after he chose to trusting the developer over and over.
I just don't know where to start to troubleshoot this problem. Please advise.
Thank you
Now, one user always get that pop-up when he tried to create a project, even after he chose to trusting the developer over and over.
I just don't know where to start to troubleshoot this problem. Please advise.
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The user has a manager access on his local address book. I haven't tried the other solution. I will give more updates later.
ASKER
I haven't tried DominoG solution because no other user has this problem. So I took that user id file and open notes with that id file on the spare PC. I tried to create a new ticket and I didn't get Trust Signer notification.
So I came back to the user and asked him to make a change on the description because that will trigger the Send method that triggers the Trust Signer notification the last time. This time the notification didn't show up. He'll let met know when he needs to create a new ticket and get the notification again.
I'm not sure what else to test or what actually caused the problem.
So I came back to the user and asked him to make a change on the description because that will trigger the Send method that triggers the Trust Signer notification the last time. This time the notification didn't show up. He'll let met know when he needs to create a new ticket and get the notification again.
I'm not sure what else to test or what actually caused the problem.
The most likely cause has been mentioned - that the user didn't have write access to their local NAB to store the result of the "trust signer" action. Sometimes this can be for silly reasons - like for instance, the user is female and just got married, and therefore their name has changed. Other times it can be because your client-side antivirus has locked down the files, or that the data directory is in a different place than some other policy implementation is expecting and that cuts off the write access. The fact you got the problem to go away by using that same ID on another PC sugegsts strongly that it is a Windows security issue, not a Notes security issue.
ASKER
ok so I copied the current database, renamed it, and I created a test user. I signed the new database with server ID then using the test account I tried to create a new project but the Trust Signer window still come up the first time the test account use it.
Is that something to be expected even after I sign the database using the server ID?
Is that something to be expected even after I sign the database using the server ID?
on the same PC that has the problem, or on a different PC? We are consiering the *local* Names.nsf which can end up having different rights on divverent client PCs, in "disadvantaged" installs...
ASKER
it's on different PC (spare/test PC). What I'm not sure is if I sign the database with server ID, should it prompt the user to trust the signer (the server) the first time they access database or not at all?
It prompts the user when the code is trying to run ReplaceItemValue method, Dblookup, and Send method. (which are all included as part of Save & Close button in the form).
It prompts the user when the code is trying to run ReplaceItemValue method, Dblookup, and Send method. (which are all included as part of Save & Close button in the form).
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've signed the database with my UserID before and it required the user to authorize the action (only the first time).
About your first paragraph, how do I check if the server ID is on the same organizational unit?
About your first paragraph, how do I check if the server ID is on the same organizational unit?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As above should solve issue long term.
Also look at Policies and Policy Settings documents within your directory as you can modify a default ECL that includes the developers ID and then have it update all machines next time they connect to the server.