Hi

Its little difficult to give a straightforward answers for scenairos like this. There is a need to analyze tracer and observe the sequence of events in order to comment further on this,

Can you please check in your tracer and see whether there is any extension point that you can utlize .

Hi,

The problem you are facing is problably with way the default form element for the login page defines the action attribute.  (The default is Web-Login but you probably already have your own)

<form name="main" method="post" onSubmit="return sendLoginRequestForm(event);" action="<pega:reference name="pxThread.pxReqURI" mode="normal" />" target="_top" novalidate="novalidate" autocomplete="off" >

The action attribute is not maintaining the orginal query string.  The first time the login is called the parameter is there because it was part of the URL being called. When the login page displayed it dropped the parameter.

For custom authentication you can do the following:

1) Create a new property in Code-Pega-Thread call SSOQueryString. 

2) In your login activity map pxThread.SSOQueryString to param.pyQueryString in a property set step.

3) Update your login HTML and change the form to also include the query string in the action attribute:

<form name="main" method="post" onSubmit="return sendLoginRequestForm(event);" action="<pega:reference name="pxThread.pxReqURI" mode="normal" />?<pega:reference name="pxThread.SSOQueryString" mode="normal" />" target="_top" novalidate="novalidate" autocomplete="off" >

4) Depending on some of your error handling etc make sure that the Data-Admin-AuthService is specifying your correct login, with updated form element, on the Custom tab for both "Credential Challenge Stream" and "Authentication Failure" stream.

Hope this helps.

--Chris