Shibboleth & Respondus / Blackboard Integration

Cantor, Scott cantor.2 at osu.edu
Fri May 25 21:02:24 BST 2012


On 5/25/12 3:53 PM, "Mark Valites" <mvalites at buffalo.edu> wrote:
>
>But not active in our implementation...

If the criteria for doing something is that nobody has to touch anything,
you can definitely consider ECP the wrong technology for your problem. I
would claim you will find nothing will  work but hacking browser flows and
having the exact issues you mentioned, but that's a separate discussion.

>If the ECP application is to communicate with our SP & IdP, I assume
>it'll need some metadata for info about them, to establish trust, etc -

ECP doesn't assume that metadata is something people want to build into
clients, and it isn't necessarily a fit.

All of the non-web solutions (Moonshot, ECP, other GSS proposals) have the
basic problem that 802.1x has, how you provision trust in the
authentication point to the client.

>IdPs & SPs have nice, clean ways to define their metadata source - how's
>an ECP application do this? Can the application creator specify a source
>of metadata in the same ways as the IdPs & SPs can?

I don't think you'd want to, but you have to write the code, so the answer
is sure, if you build it to.

It won't address the bootstrap question of identifying the IdP though.

-- Scott



More information about the users mailing list