requestParameters getting lost during local storage interactions in custom logout flow

[Cantor, Scott]

On 4/11/19, 9:56 AM, "users on behalf of Liam Hoekenga" <users-bounces at shibboleth.net on behalf of liamr at umich.edu> wrote:

> We are altering the logout flow such that /idp/profile/Logout can take a URL to redirect to as a possible argument.

You should definitely *not* alter the flow, that will turn every patch into a major ordeal. Altering templates is fine. Alternatively, your own flow using only public classes and APIs is also an option but that's a lot of code copying.

> I have found that if we're using client-side storage, the requestParameters present at the beginning of the transaction
> are lost as soon as the flow invokes the client-side storage.  Is there some structure that we could stash our return URL
> in for later retrieval?

Conversation and flow scopes in WebFlow can hold data across requests, and 3.4 includes a context class type that can be added to the context tree [1] that just contains a map.

-- Scott

[1] org.opensaml.messaging.context.ScratchContext