Research and Scholarship and filter by relying party

[Tom Scavo]

On Tue, Mar 4, 2014 at 4:39 PM, Tom Scavo <trscavo at gmail.com> wrote:
>
> Seems like you're talking about campus policy (which is fine of
> course, campuses can do anything they like) but in a cross-domain
> scenario, authorization is not the IdP's responsibility. Your job is
> to authenticate the user and provide attributes (or not, subject to
> policy). The SP decides what to do next.

Oh, and I should add: this is what it means for an IdP to be
"discoverable." Very Soon Now, InCommon IdPs will have the option to
self-assert an entity attribute that declares the IdP to be
"discoverable," which means you *want* to appear on arbitrary
discovery interfaces. If you don't want to appear on discovery
interfaces (except those of SPs you choose to interoperate with), you
simply do not declare the entity attribute. SPs can use that entity
attribute to build their discovery interface on-the-fly.

Tom