Question

5
Replies
1067
Views
 Iain Adamson (IAINADAMSON)
Lloyds Banking Group
Pega Engineer
Lloyds Banking Group
GB
IAINADAMSON Member since 2012 4 posts
Lloyds Banking Group
Posted: January 21, 2019
Last activity: November 15, 2019
Posted: 21 Jan 2019 5:14 EST
Last activity: 15 Nov 2019 16:31 EST
Closed

Can changes to the administrator@pega.com Operator ID be saved from another Operator ID in Pega 7.22

We have a Pega Smart Disputes (Pega 7.2.2) cloud implementation and we have a requirement to change the password of the administrator@pega.com OperatorID from another Operator ID.

According to https://community.pega.com/support/support-articles/unable-change-password-administratorpegacom, changes to the pega admin operator ID can only be saved from the Operator Profile screen not from the Operator ID screen (which I have proven to be correct). Therefore no other Operator ID can save changes to this Operator ID.

Is there a specific role or another privilege that allows changes to be saved to the Pega admin operator ID from the Operator ID screen, so changes can be saved by a different operator. Or is this simply not possible in Pega 7.2.2.

***Edited by Moderator: Pallavi to update platform capability tags***

Pega Platform Low-Code App Development Security Support Case Exists
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 2 years ago
Posted: 21 Jan 2019 6:16 EST
Abhishek Kumar (kumaa33)
PEGA
Senior Systems Engineer - Cloud
Pegasystems Inc.
IN

PegaRULES:SysAdm5 is the access role.


pzModifyAllowed on class Data-Admin-Operator-ID


Please check whether the above access role and above mentioned access when is there in the ARO.


I think that is required to modify the administrator operator ID.


Let me know if that helps.There are other options also to modify.


 
Posted: 2 years ago
Posted: 28 Jan 2019 5:09 EST
Iain Adamson (IAINADAMSON)
Lloyds Banking Group
Pega Engineer
Lloyds Banking Group
GB

PegaRULES:SysAdm5 is not available, PegaRULES:SysAdm4 is and this role includes pzModifyAllowed (write instances) on Data-Admin-Operator-ID

I have tested an OperatorID with an AG that includes only this role and get the same results when saving administrator@pega.com:


This record has 1 error(s) in 1 place(s) .

—

You are not authorized to create, modify, or lock instance DATA-ADMIN-OPERATOR-ID ADMINISTRATOR@PEGA.COM



Please can you advise what the other options are to enable me to save this this OperatorID from another OperatorID