User Configurable Flow at /idp/

[Cantor, Scott]

Summary of this issue here:

https://issues.shibboleth.net/jira/browse/IDP-474

In a nutshell, we can map /profile/* along with /status and it will work,
but the caveat is that once you map a directory tree like that, any flow
ID you append to that path will work.

So if you add a mapping for /custom/* or what have you, the profile flows
will also be "mounted" under that tree. I don't think there are likely
scenarios where that causes a problem other than making it possible to run
flows that might not work properly, but it's not inconceivable this would
create a problem in a particular case.

Marvin, does the CAS flow need a particular location to be compatible with
something? If so, we'll need to have a mapping for that.

-- Scott