I have a set of agents that have been running 100% for over a year. Some adjustments were made (not certain what) to the Domino server… ironically, it is the same time the console started throwing agent execution errors. I’m running as “run as web user” and all users are authenticated. All users have rights in ACL. The restriction type is #2 in the agent properties. Any ideas? What field in the server doc’s security section should be checked. I had the admin sign the Dbs with the server ID… and all is fine! I have to sign with my “active ID” after a design update… but I appear in the run on bahelf of… field (in admin group) in the server document. It seems to be my ID… but what could be the issue?
Subject: Run As Web User & Sudden Problem
The agent signer has to be in the field “Sign agents to run on behalf of someone else:”.
The server is always trusted, so agents will run when signed with the server id, even if the server name is not in that field.
Subject: Run As Web User & Sudden Problem
Does the user you are running the agent under have restricted agent rights in the server configuration?
Subject: RE: Run As Web User & Sudden Problem
The “run as web user” is checked so authenticated users can excute the agent. I thought this ran off the agent signer’s name… as far as thet security field.
Subject: RE: Run As Web User & Sudden Problem
Sorry, I think I kind of misread your original post.
“Run as web user” should override the agent signer security wise. But I think that if the agent’s security level is set to 2, all authenticated web users would have to be in the “Run unrestricted methods and operations” field on the server document. This is certainly not what you want.
Subject: RE: Run As Web User & Sudden Problem
Thanks… this is a bit of a mystery because the agent properties (run as web user & restrictions #2) have been unchanged for 18 months and running fine. It was only after the admin made changes that it started happening. When she put my name back in the “run agents on behalf of someone else…” field <+ others>, it started to work again. The error when someone else ran it was my user name as signer and effective user as test servlet <a servlet runs when user executes agent - the call to the servlet is embedded within the agent> I know that all users could not possibly be in these security fields… maybe I’ll need to look at changing it to another security level in agent properties. It just does not make sense that it would change in the 1st place.