Can the below Default accounts be either Disabled or removed? I could not find documentation on these. Are there any repercussions of disabling them?
| Operator |
AccessGroup |
Disabled (Y/N) |
| External |
PRPC:Unauthenticated |
N |
| ExternalInviteUser |
PRPC:Administrators |
N |
| PRPC_SOAPOper |
PRPC:ProcessArchitects |
N |
| [email protected] |
PRPC:DatabaseAdministrators |
N |
| [email protected] |
PRPC:PortalUsers |
N |
| uiservicemanager |
PRPC:UIServiceManagers |
N |
| [email protected] |
PRPC:Administrators |
N |
| aesremoteuser |
PegaAESRemote |
N |
| MarketingConfigurationAdministrator |
PegaMarketingConfiguration:Agents |
N |
| ExternalNPSUser |
PegaNPS:Administrators |
N |
| [email protected] |
PegaCRM-SFA:Services |
N |
| OfficeAdmin |
PegaCRM-SFA:SysAdmin |
N |
| DMAppAdmin |
PegaDevOpsFoundation:Administrators |
N |
| CSRTemplateOperator |
UMECASysAdmin |
N |
| UMECASysAdmin |
UMECASysAdmin |
N |
| UMESysAdmin |
UMESysAdmin |
N |
| UMECSRTemplateOperator |
UMECACSR |
N |
| UMECSUSER |
UMECSUSER |
N |
| CSUMEUser |
UMECSUSER |
N |
| CSSelfServiceUser |
CSSelfServiceUser |
N |
| ExternalKMUser |
ExternalKMUserAG |
N |
| IntSampleUser |
IntSample |
N |
| KMServiceUser |
KMServiceUserAG |
N |
| ExternalApprover |
KMApprover |
N |
| KMServiceUser |
KMServiceUserAG |
N |
| aesremoteuser |
PegaAESRemote |
N |
| [email protected] |
uvu:user |
N |
@CarolynB6335
Most of these Operators are not disabled by default. Except [email protected] [ for any Administrative activities like Installing HFIX’s etc.,] and DMAppAdmin [Used in DevOps pipelines], most of th ID’s can be disabled,
However test the application to ensure it’s not breaking anywhere.
@CarolynB6335
Hello,
You can first check on last login date to see whether there’s been any connection recently.
We disabled most of them (as mentioned in previous comment, you indeed need to be sure it’s not used in any processing)
But by default, it’s normally not, it’s OOTB users and your application should use dedicated users.
Yet, please make sure that [email protected] is available (or at least one your user with prpc admin access)
This is your last option to connect the system in case your application is “corrupted” (broken AG, Pb with ruleset, Pb with anything for which your application will not come up): for such situation you’ll have to start your application as prpc and then you’ll need an admin user with prpc:administrators access group. if you don’t have any, then you’re fully stuck.(make sure prpc system / system name has not been deleted of course)
Regards
Anthony
@CarolynB6335 if Anthony’s answer resolved your issue could you mark ‘Accept Solution’ against his reply?