Shibboleth IdP as the hub in a hub and spoke federation

[Cantor, Scott]

On 3/3/14, 5:44 PM, "Scott Koranda" <skoranda at gmail.com> wrote:
>
>If I am willing to pay the price/overhead of developing my own login
>handler
>due to other motivations, there is no particular reason to have to use the
>External login handler, correct?

Yes. All it really is is just a slightly narrowed convention for
interfacing to the requirements of a full custom handler, and those aren't
really that much more complicated.

>Indeed using the MCB as a base and developing a MCB sub-module(s) to
>act as a proxy in conjunction with the Shibboleth SP and Apache is also
>a viable approach correct?

I would think so, but from my own experience with something similar to the
MCB, you could run into assumptions it makes about the UI and how to
branch off and then resume processing in the MCB code. Obviously Paul
would know much more than I on that. I guess thinking of that other
thread, it's using container sessions to some extent, so that would
probably address part of that problem.

The other point is that there's currently no built-in data connector for
attribute lookup that can pull from headers/variables.

-- Scott