Question
tcs
IN
Last activity: 22 Jan 2016 8:26 EST
while log-in using LDAP authentication service log-in url we are getting error
Hi,
I have attached screen shot and tracer details please suggest on this issue.
Thanks
RajaSekhar
Accepted Solution
Updated: 21 Jan 2016 16:28 EST
Pegasystems Inc.
US
Pegasystems Inc.
US
Can you check if your data-admin-authservice "Credential Challenge Steam" defined (under Custom tab)?
Accepted Solution
Updated: 21 Jan 2016 16:28 EST
Pegasystems Inc.
US
Hi Rajesekhar,
I can tell you are using PRCUSTOM style authentication.
The error: "No Failure response set by custom authentication" only occurs when the out parameter pyFailMessage is blank or null and no clipboard page was returned in the out parameter pyOperPage. Sending no value for pyOperPage with a failure message is pyFailMessage is how you do error handling. When both are blank it's an invalid state so we throw the exception.
From the tracer output you provided I can't tell you what is going on with out looking at the activity. You have a customized version of AuthenticationLDAPVerifyCredential in you unauthenticated ruleset.
It's either logic skipping the Property-Set step that sets the param.pyOperPage = @java("myStepPage")
Or
In your error handling block there is no step taking the local.errorMessage and setting it to param.pyFailMessage.
Hope this helps.
tcs
IN
Hi Chris,
Your solution worked for me. inmy case "error handling block there is no step taking the local.errorMessage and setting it to param.pyFailMessage" this was not happened. i have resolved the issue. Thank you Chris.
Thanks
RajaSekhar
Hi Rajesekhar,
I can tell you are using PRCUSTOM style authentication.
The error: "No Failure response set by custom authentication" only occurs when the out parameter pyFailMessage is blank or null and no clipboard page was returned in the out parameter pyOperPage. Sending no value for pyOperPage with a failure message is pyFailMessage is how you do error handling. When both are blank it's an invalid state so we throw the exception.
From the tracer output you provided I can't tell you what is going on with out looking at the activity. You have a customized version of AuthenticationLDAPVerifyCredential in you unauthenticated ruleset.
It's either logic skipping the Property-Set step that sets the param.pyOperPage = @java("myStepPage")
Or
In your error handling block there is no step taking the local.errorMessage and setting it to param.pyFailMessage.
Hope this helps.