Handling a parameter to logout flow

[Cantor, Scott]

> Using #parse("logout-finish.vm") may be a good way to make the finishing of
> a SAML SLO request customizable.

I'm not in a head space in which I can even think about logout. Maybe somebody else is.

The entire UI has to be rewritten because it's not accessible, and there are assumptions built into it that people don't want. If you want to propose specific patches, you can file them in Jira, but you're possibly better off essentially requesting specific features in conjunction with any particular proposal, because any patches probably won't apply to whatever we end up with after all the contortions.

I would agree that any place we have significant logic we probably want to move into included files, but I can't say whether any specific boundary will be safe or not. There's just a lot of intertwined logic.

As a general response? I don't think expecting a user to click something to "complete" the flow is an option, and I also don't think a timer is workable, because it means losing access to the very critical list of failed logouts on the results display. So, I can't see us doing that, no. The return parameter just isn't workable to me in a single logout scenario.

-- Scott