We have implemented Single-sign-on (SSO) using GetWebTicket.aspx, and being redirected to a QlikView document with section access / data reduction, and strict exclusion.
The user logs in to a 'My page', where he/she has a user space, and a button to go to the QlikView model, where he/she can only see more personal data.
This works pretty well for all existing users.
However, when we create a new user in the legacy system they can log in to the user space straight away. However, the QlikView model does not yet reloaded, and does not yet know of the new user. If a new user tries the QlikView-button, the following happens:
Legacy asks QvAjaxZfc/GetWebTicket.aspx for a ticket for user <newuser>.
QvAjaxZfc/GetWebTicket.aspx replies with a valid ticket.
Legacy redirects users browser to QlikView's QvAjaxZfc/Authenticate.apsx with the web ticket, and qvw-name.
So far, so good.
Authenticate redirects user to AccessPoint.aspx? with open=&id=<qvs-server>|<qvw-file>. This return 404 and a blank page, since the users has not been loaded into the model
This is not really incorrect, but a blank page gives a very bad user experience.
Is there a way to redirect a AccessPoint.aspx 404 (Not found) to another URL?
For example the url provided in the 'back=' argument to Authenticate.aspx? Or even a static url?
We have this issue at two places. One using IIS and the other using QV WebServer.
A solution for both, or one of them would be greatly appreciated.