idpv3 and web flow : flow-location or flow-location-pattern ?

[Tom Zeller]

> I think the former.

I wonder if we played rock-paper-scissor how many times we would tie.

>> <webflow:flow-location id="SAML2/POST/SSO"
>>path="/SAML2/sso-post-flow.xml" />
>> <webflow:flow-location id="SAML2/Redirect/SSO"
>>path="/SAML2/sso-redirect-flow.xml" />
>
> Yes, in effect handler.xml in V2.

I was not sure if deployers customized the default endpoints in
handler.xml, so I sorted the InCommon and UKfed metadata and it looks
like most folks do not, meaning only a few (<3) IdPs use non-vanilla
URLs.

>>I think I prefer mapping implicitly via the file system and
>>flow-location-pattern, mainly because profile-to-flow mappings are
>>thus external to the war, if I understand correctly.
>
> I wouldn't think they would be, which is one reason I'm not in love with
> the idea. If it is, I might change my mind. But I'm pretty sure based on
> my limited playing around, all that was relative to the class path. Maybe
> it could be pointed to the conf tree, but even then, who wants deep trees
> in conf/?

Well, we need to talk about flows being external to the war pending
more knowing. I also know you prefer a non-exploded war as well. I
guess me too, in some ways.