User Configurable Flow at /idp/

[Cantor, Scott]

On 9/2/14, 9:00 PM, "Marvin Addison" <marvin.addison at gmail.com> wrote:

>Root, index, default, landing page; it goes by many names. I would
>like the ability to render content at /idp/ to display a friendly
>landing page instead of the default behavior or sending a 404. In v2
>you could drop jsps under the root of the WAR file and they would
>render; so I had an index.jsp that worked fine for that purpose.
>That's not possible in v3 since the servlet-mapping for the idp
>servlet is /*.

We can still exempt some content from that using the web-mvc resources
configuration. We could also just special-case the /status flow for
compatibility, but require future flows live under either /profile or
maybe /profile plus some additional option(s) for user flows, but leave
the root open.

Just mentioning options.

> That's ok because what I really want is a flow at that
>location anyway.

That's an option I guess, but I don't know if most people would share that
view...

> Initially I would like a simple static landing page
>to replicate our v2 behavior, but I would like to build a dashboard
>that can get at the IdP session to display a list of services visited
>in the session. A user-configurable flow that runs at /idp/ would
>provide the flexibility to do either.

So would a JSP there that forwards to a flow...

>Aside from the slight complication of getting a sane flow ID for the
>/idp/ URI, it seems like this should be straightforward: ship a flow
>under /flows that renders a 404 by default, but that the user can
>modify to achieve other behaviors. As for getting a flow ID for what
>is effectively an empty path, you could extend DefaultFlowUrlHandler
>to have some special handling for the root context path.

Like Tom, I don't know if I favor extending that just to make it possible
to skip a simple redirect/forward from index.jsp

Obviously we need to support a landing page regardless, just a matter of
how.

-- Scott