Some providers may have failure modes that leave the user stranded at the IdP.
We should redirect these users to a cute landing page that apologzes for the inconvenience, tells them which server (SP, upstgream login, etc) caused the error, and have a customizable text on who to contact to get help.
component: Documentation => UXD
milestone: => 1.0
status: new => assigned
milestone: 1.0 m4 => 1.0
This is primarily intended for 400 errors, though perhaps 500 would go here as well.
Ideally there would be links to help guide the user back to their application.
milestone: 1.0 => Backlog
milestone: Backlog => 1.1
status: assigned => new
milestone: 1.1 => 1.2
I think this is somewhat already done. There are customizable error handlers and templates for 400, 401, 404 and 500 errors. Unfortunately the cherrypy error handler is limited to just status, message and traceback so I don't see a way to pass a ton more information into the error handling page.
The current limitation is that each error type will show just the message that was raised. I think this may need to be handled at a lower level. Each raised message needs to include more descriptive information. And doing so one may lose some amount of customization (e.g. per-SP admin contacts).
More information may be doable via a helper which cobbles together as much info about a given error as it can and then raises the 4xx exception.
milestone: 1.2 => Backlog
Metadata Update from @nkinder:
- Issue set to the milestone: Backlog
to comment on this ticket.