Question
Corporation Service Company
US
Last activity: 22 Aug 2017 9:05 EDT
User always gets redirected to Change Password
Hi,
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***
Accepted Solution
SMS Management & Technology
AU
Thanks MandarK6 for your response.
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.
Regards
Murali
Pegasystems
US
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.
/Eric
Corporation Service Company
US
Hi,
I traced, I see the activity being called pzShowCPHarness. I am unable to get, how this is getting called. The history of the activity says, its called by system.
Pegasystems Inc.
US
First we would need to know if this is standard Pega Authentication, or some customized or SSO implementation.
If you trace, please be sure to turn on all when events, declaratives, interaction and flow checkboxes
Additionally if you can use Fiddler to provide a web level trace as well, that would also help understand what is going on.
You may be having your session cookie dropped, and that can't be seen in a Pega Trace.
Does the issue occur through a load balancer, or other gateway type network device?
Does the issue occur when connecting directly to the Pega Server?
Please attach zipped pega and fiddler trace if you still can't find the reason.
Corporation Service Company
US
Hi,
Users are authenticated using standard pega authentication.
I will do the trace and fiddler and attach it once done. Please let me know how can I share the tracer events and fiddler.
Pegasystems Inc.
IN
Hi Jagdish,
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.
Thanks!
~ Vidyaranjan A V | Community Moderator | PegaProductSupport | Pegasystems Inc.
SMS Management & Technology
AU
Hi Vidyaranjan
We are facing this issue in Pega 7.2.2
Could you please let me know if SR-B11283 has been resolved and a hot-fix available to request?
Thanks & regards
Murali
Pegasystems Inc.
US
Hi Murali!
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.
Thanks!
SMS Management & Technology
AU
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?
Regards
Murali
Accepted Solution
SMS Management & Technology
AU
Thanks MandarK6 for your response.
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.
Regards
Murali