Question

Standard agent's security context is not switching to pyAccessGroup of the queued requestor

V7.1.8 - Standard agent is always running under PRPC:Unauthenticated context (PegaRULES:Guest role) and is not switching to the authorization context of the queued requestor. Any ideas on what might be the issue or if this is a known issue?

Edit: Issue is resolved. System name was changed and the new Batch requestor was using Unauthenticated accessgroup instead of the batch access group. We had to clear the cache and restart to get it working again.

***Updated by moderator: Lochan to update Categories***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Correct Answer
January 10, 2017 - 3:09pm

Issue is resolved. System name was changed and for some reason the new Batch requestor was using Unauthenticated accessgroup instead of the batch access group. We had to clear the cache and restart to get it working again.

Comments

Keep up to date on this post and subscribe to comments

Mod
December 25, 2016 - 11:24pm

Hi Mr.Ashok,

Glad to hear that the issue was resolved! Please share the resolution so that it helps other members who have the same question.

Regards,
Lochan  |  Community Moderator  |  Pegasystems Inc.

Lochana | Community Moderator | Pegasystems Inc.

January 10, 2017 - 3:09pm

Issue is resolved. System name was changed and for some reason the new Batch requestor was using Unauthenticated accessgroup instead of the batch access group. We had to clear the cache and restart to get it working again.

Mod
January 10, 2017 - 9:31pm
Response to Mr.Ashok

Thank you for sharing the solution out here!

Lochana | Community Moderator | Pegasystems Inc.