OperatorID page under requestor pages (Clipboard) does not contain the pyPwdCurrent property for sso user
OperatorID page under requestor pages (Clipboard) does not contain the pyPwdCurrent property for sso users. Because of this availability feature is not working for them as expected. its works fine for non sso users as the property pyPwdCurrent is present for them
when i open the SSO enabled operator instance and view xml, i could see pyPwdCurrent property but when i see the clipboard of the loggedin SSO operator, i could not see the property under Operator ID page. This availability use to work before for SSO users. we have updated the version to 7.1.9 recently hence would like to know whether it is a product bug or something else?
***Updated by Moderator: Lochan. Removed user added helpme tag. Apologies for confusion, shouldn't have been an end-user option; updated 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.
Thank you for posting your question on the Product Support Community.
It looks like the question is being investigated in the SR-A94030. Later, feel free to update the thread with the resolution steps, for it will benefit the community users who come across same question.
~Vidyaranjan A V | Community Moderator | Pegasystems Inc.
Is there any resolution identified for this issue ?
We face the same issue for few support users who were not able to perform any update action due to the above error.
When we checked the individual operator's XML --> pyPwdCurrent is empty though other attributes are similar compared to an working operator id except the pyPreferences page which is present only in the working operator ids.
Would be great if you share me the resolution applied.
I believe your users are also not able to set the unavailability when they login from SSO ? If yes then please make sure user id has valid password so that validation check for unavailability should go through. Let me know if you need any help in this.
Havent tried the "Unavailability" however I am facing this issue when I try to update the skill of an user whose pyPwdCurrent is empty (in PreviousVale page) when i checked it from clipboard xml. But those users arent facing any issues w.r.t to login via LDAP which is very strange.
As a workaround, we just clicked the "SAVE" of their operator id in order to update the operator instance to store password and it worked there after. However I am looking for a permanent solution , as we cannot SAVE such operator ids in production.