Question
Header Changes for PingAccess
Siteminder to Ping Acess Migration is happening for GMOF aaplication.
The Ping Access agent is installed too, the problem we are facing currently
is after logging from SSO (after putting USerID and password) - Pega rules Process Commander
page is opened - The error msg which pops up is ' Unable to create an account.
An incorrect User role for user: ZKDQT3L (User ID)'
We understood that the there may be some header changes to be done for Ping Access. Currently Siteminder is using headers with http in the prefix and Ping Access do not need http Headers:UID,MAIL,ROLE,EMPLOYEENUMBER,FIRSTNAME,LASTNAME,CN
Can you confirm if the same has to be done ? or what would be the solution for the error faced ?
Thanks Chris!
I Found some of the required headers in authentication activity. Seems like i only have read onl access so unable to add your given code.
Will you be able to help me on process required to get write access ?
<message edited by moderator Lochan to remove account information>
Hi Sonali,
I just spoke to our team and they're going to continue to work with you on your Support Request regarding this.
I've notated it within your original post so that we may keep track for you and update this post with your resolution.
Thanks!
Thanks Marissa.
I am able to edit now but not yet sure on Values. Thus, i have raised a SR for the same SR-16855.
Hope to get a correct response on the same :)
Accepted Solution
Hi @DeepaK73,
You would need to open a Support Request and ask for that Hotfix and GCS will obtain that for you.
Hi,
You will need to debug your custom authentication activity and see what is going on. That error message should be being returned somewhere in your login activities.
My guess is that when you changed SSO providers the HTTP header names that are sent from Ping Access to PRPC have changed. This is causing the logic in your login activities to be missing data and returning the error message.
If you want to know what headers are being sent to PRPC from ping access you can add this code to a java step at the top of your login activity:
javax.servlet.http.HttpServletRequest request = (javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest");
if (request == null) {
oLog.infoForced("NULL REQUEST OBJECT!");
}
else {
java.util.Enumeration e = request.getHeaderNames();
String header = null;
while (e.hasMoreElements()) {
header = (String) e.nextElement();
oLog.infoForced(header + ": " + request.getHeader(header));
}
}