User Configurable Flow at /idp/

[Cantor, Scott]

On 9/5/14, 6:02 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>
>BTW, do you have any insight from your testing as to why mapping /* does
>work? Maybe MVC handles that case specially? Ultimately it's just about
>getting the MVC servlet to run the web flow code to do the handling,
>right?

Never mind, I found the webflow class that's causing this
(DefaultFlowUrlHandler). When you map a servlet based on a path, and
include additional path info, the flow name is derived solely from the
pathinfo and the "app servlet path" is dropped.

If we wanted to control this, we could implement our own subclass, but
that's not a public API, so that's not ideal (and neither is copying the
Default implementation to avoid subclassing, though we could).

A possible workaround is to change the flow IDs we define to omit the part
we actually put into the servlet-mapping, but that has the downside that
apart from the /profile/* flows, the rest of them don't really have
unique-ish names when the authn or c14n prefix is dropped.

I need to do a bit more playing around. It's possible there are some
subtleties to this because in fact the only flows we intend to actually
run as top level flows via URL are in fact the /profile flows (and
/status, but leave that aside).

-- Scott