User Configurable Flow at /idp/

[Marvin Addison]

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 /*. That's ok because what I really want is a flow at that
location anyway. 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.

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.

I'm happy to work up a patch for this functionality, but I wanted to
float it here to get feedback.

Best,
M