Shibboleth Developers

["Bruc Liong" <>]

Title: RE: [Shib-Dev] [IdPv3] Consent Engine Work

> I've been involved in more than one brainstorming session about coming up
> with iconography to represent "typical" policies that would be
> understandable to users, and I could imagine embedding identifiers of that
> sort in the metadata rather than expecting users to read detailed policies,
> which we know they won't do.

From what we've played during MAMS Federation, IMHO putting things in metadata has the added benefit that the IdP and SP can exchange requirements and simplify user's experience dealing with "just a bunch of attributes". SP can asks certain attributes, IdP can present to user the experience whether/not certain service levels can be obtained.

This complicates things a bit (the idea of service levels seem to deter some ppl), but at the end would result in much more scalable design compared to letting the users second-guessed attribute requirements of the SPs (or letting IdP admins exchanging requirements with all known SPs about their requirements).

Bruc