finger pointing

[Paul B. Henson]

Every now and again we get complaints that the idp is very slow and it takes a long time to log in. Invariably, it turns out to have nothing to do with the idp, but rather it is the remote service that is being unresponsive. Unfortunately, after the idp has completely finished its task and redirected the browser to the service, the browser continues to show the last screen from the IDP (in our case, saving session state, as we are using client-side storage). This screen is displayed until the remote service responds and the browser renders whatever it provides. This causes end-users to think the idp is the cause of the delay.

Perhaps an additional screen/content could be provided for the transition between idp and remote service to more clearly indicate that the browser is waiting for a response from the service? I guess the simplest thing to do would be replace the current client-storage-write.vm content with something else like "waiting for remote service to accept authentication", but would a more clean implementation be to add an additional view to the end of the flow with a separate template to display? Is the latter something that would be of interest for general inclusion into the idp?

--
Paul B. Henson  |  (909) 979-6361  |  http://www.cpp.edu/~henson/
Operating Systems and Network Analyst  |  henson at cpp.edu
California State Polytechnic University  |  Pomona CA 91768