we installed a fresh Pega 8.3 on an "empty" Oracle DB by using the installation Wizard.
Here we have to provide a temp Admin password as you know, which I did. After trying to log in for the first time a message popped up to change the password, which I did. Then I was logged in and checked the Administrator@pega.com operator and changed the password again and noted it down.
One day later I´m trying to log in, it doesn´t work, neither with my initial pw, nor with the new updated pw.
I read inside Pega community and used prpcUtils, which I did the following way:
Create an Operator record (on another Pega installation 7.1.9) with PRPC:Administrator access group, export it via Product rule / Zip file. Then I imported that product via prpcUtils, which was a success, the new operator record is also visible on our 8.3 Oracle DB (pr_operators table).
Now when I´m trying to log in with the new operator credentials the message pops up: "Your account has been disabled, contact your system administrator".
What else can I do ? How come the pw update doesn´t work properly although I did everything according to the installation guide / via Designer Studio ?
I assume my intermediate pw is now the needed password for my Administrator Operator, but I haven´t noted that one down since I changed it after I was logged in initially as I mentioned.
Appreciate your help in advance.
***Edited by Moderator Marissa to update Product Version tag***
this helped, we missed to set insecureOperators = true when importing our rescue admin operators. Many thanks for the suggestion.
However after I could again log in with the Rescue user I created new admin users (with "special" names like ProjectAdmin@pega.com) and updated the password in the Operator rule form. When I tried to log in with these new users in a new session it didn´t work still. It acted as if I´m typing the wrong pw, which I 100% did not. Thank God I still kept the Rescue User logged in (from another browser session) and tried the following: For my new ProjectAdmin@pega.com operator I checked the box "Force password change on next login". Then I tried again, and it worked after changing the pw. So I am not sure if our configuration somehow is not correct (DB privileges for Rule / Data Schema Users or the like?) but this behaviour is quite weird :-)