requestParameters getting lost during local storage interactions in custom logout flow
cantor.2 at osu.edu
Thu Apr 11 10:34:35 EDT 2019
On 4/11/19, 10:19 AM, "users on behalf of Liam Hoekenga" <users-bounces at shibboleth.net on behalf of liamr at umich.edu> wrote:
> I'd rather not alter the flow itself, but it seems that by the time it gets to the template, requestParameters is lost and all
> that's available is the conversation state.
Yes, but that's because this feature just isn't supported. We will never use them ourselves, but I'm willing to code in a default capture of any parameters into that specific flow/URL into the scratch context if somebody files a request for it.
> Is it possible to extend or replace a system flow?
Extension is only possible in the ways we explicitly support that don't involve touching system files. Replacement isn't really a thing, you deploy new flows and they ideally get registered to run at a different location, but it is possible in the latest versions to replace and override the use of existing locations altogether in a pinch. Just not generally necessary, particularly in this kind of case when the original URL is totally arbitrary anyway.
Proprietary locations that aren't in metadata should never be shared with anybody and should go through redirection of some kind to separate the published location from the mechanics of the software. Mine is at /cgi-bin/logout.cgi
More information about the users