Disable Operator and Force password change on next login are enabled for Operator ID After Upgrading to 7.4 with PostgreSQL and Tomcat
We have upgraded application from PRPC v7.2 to PRPC v7.4 and migrated Database from IBM DB2 to PostgreSQL and Web servers from IBM Web Sphere to Apache Tomcat.
After the data migration we observed that most of the operator records has Disable Operator and Force password change on next login check boxes are enabled as shown in the picture. This is happened for the three regions - DEV, QA and Model regions after the data migration and PRPC setup.
Can anyone knows what is the reason for it and is there anyway to make these check boxes unchecked (without writing one time utility to set the properties to false) ?
***Updated by moderator: Lochan to update platform capability***
Pegasystems Inc.
US
The security changes have been applied to the OOTB Pega operators in Pega 7.4. Here is the information from the release notes regarding the change.
To improve security, Pega® Platform now requires the following:
The security changes have been applied to the OOTB Pega operators in Pega 7.4. Here is the information from the release notes regarding the change.
To improve security, Pega® Platform now requires the following:
- During deployment, you must configure a password for [email protected].
- The administrator must enable new out-of-the-box operators.
- The administrator and new Pega-supplied operators must change their passwords after the first login.
These requirements replace the optional secured mode in earlier versions of Pega Platform.
Pegasystems Inc.
IN
Hi,
Thank You for the reply. Got to know this.
As we can enable the disabled operators through below navigation but did not find any wizard to disable "Force password change on next login" check box other than writing one time utility to update the pyChangePasswordOnNextLogin property to false or updating each operator record in Designer Studio.
And the enabling the disabled operators also difficult since we need to check each and every operator and need to click on Enable selected(we have 3000 operators its difficult to for all one by one)
Designer Studio - Org & Security - Authentication - Operator Access - Operator Access
The only way to update these Disable Operator check box and Disable Operator check box at single run is to write an Utility to get all the operator records and set pyOperatorIsDeactivated and pyChangePasswordOnNextLogin false and save them.
Please do let me know if we have any other option to update these other than activity ?
Thank You.
Adaps
IN
Below link might help you
https://collaborate.pega.com/question/how-force-password-change-next-login-end-user
Pegasystems Inc.
IN
Hi,
I do not want add it, I want to remove.
Adaps
IN
Can you check this in Security policies?
Pegasystems Inc.
IN
Security Policies already been disabled. I just want to update these pyOperatorIsDeactivated and pyChangePasswordOnNextLogin properties.
Accepted Solution
Pegasystems Inc.
IN
Hello All,
We had raised an SR for this. Team suggested to write an activity to update both properties for the operators.
Pegasystems Inc.
US
Pegasystems Inc.
IN
Hi Marissa,
SR-C62899 is created for this one.