Posted: 28 Dec 2016 11:11 EST Last activity: 22 Aug 2017 9:05 EDT
User always gets redirected to Change Password
We are using Pega Security Policy for our application.
In our application a public User or a Interner User can click on Register link on the login screen and create a profile for itself. We send email and ask user to confirm. Once the user has confirmed registration, when user tried to login by entering User ID/Password, Pega always redirects the user to change password, becuase its a new user..
Issue: User has just registered by entering ID/Password. We should not redirect it to Change password.
Please help, how do we handle this.
According to my research, Pega is calling pzShowCPHarness activity from engine to redirect user to change password. How can we change this as per our requirement.
I raised a SR (SR-B11283), but they say it should be handled in the product community.
***Updated by Moderator: Marissa to add SR Exists Group tag to thread***
I don't have a quick answer, but I suggest you trace it and see what logic is being used for determining whether to prompt for a password-change, and see if there are configurable settings or parameters referenced that you may be able to change.
While reviewing the SR details, I read that an enhancement request has been submitted for your use case. I have tagged the feedback request id in the related support case number section along with the issue description above. You may follow up with your Account Executive for updates on the progress of this request.
There doesn't appear to be a hotfix for this that I can see. We did submit an enhancement request which is noted in the original post starting with FDBK. Please contact your Account Executive with that FDBK ID for next steps.
We have raised this issue with our account executive. Seems we are not going to get any fix for this as this is OOTB behaviour by design as per Pega product team. It is very hard to believe that this feature is by design! I feel this is very bad user experience.
Please let me know if anyone implemented a work-around for this?
Please ignore this. This issue got resolved when we tried to create operator record for newly registered user via model user. Earlier were creating operator record for newly registered user y creating a new page of Data-Admin-Operator-ID and then persisting this.