Get a Parameter in Web-Login Page
Hi ,
This is related to a parameter we use to display selected content ( based on User's language ) in web-login.html.
The URL to access the application (pega URL) will contain a parameter say lang . V ( http:pegaurl/!STANDARD?lang=es_US )
Based on the value of lang - the web-login.html will display selected content to user.
The problem occurs when there is a validation error in the Custom Authentication activity. Say the user credentials do not match .
Then the web-login page is shown to user & at this point the web-login page cannot get the value of lang . So it displays the default content.
We tried to set a param called lang in the Custom Authentication Activity as an Out Param . But it did not work.
We then tried to get and set the value of lang to the query string using a pxThread Property.
This way the URL always contains "lang=en_US" . But when we access this property using :tools.getParamValue("lang") it still does not return a value.
Can you help me with setting the lang variable correctly so that the web-login file can get it ?
Thanks,
Smitha R
***Updated by Moderator: Vidyaranjan| Included Categories***
Pegasystems Inc.
IN
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 .
Pegasystems Inc.
US
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" >
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