If you attempt to use a customized Authenticate.aspx which was developed to work with 11.00IR, then it may no longer work after upgrading to a later version of QlikView.
You may experince a blank web page.
If you trace with fiddler you would notice that in 11.00IR there is a "302" response and an automatic redirect to the place specified in the "try" parameter (the expected behaviour).
In later versions, unless you have already recoded the Authenticate.aspx, there would be a "200" response and no redirection takes place.Environment:
QlikView 11.00 SR 1 and up
In later versions, a call to QlikView.AccessPoint.User.SendLoginResult has been removed from the function QlikView.AccessPoint.User.GenericAuthentication.
This means it does not get automatically called automatically anymore, it is now necessary to call SendLoginResult separately.
So in previous versions it was enough to do:
But in later versions it is necessary to do:
bool authenticationresult = QlikView.AccessPoint.User.GenericAuthentication(context, user);
QlikView.AccessPoint.User.SendLoginResult(context, QlikView.AccessPoint.User.GenericAuthentication(context, user));
It is the SendLoginResult that redirects the clients.