Evolving Attribute Release Policies for campuses

Wessel, Keith kwessel at illinois.edu
Thu Apr 7 11:17:06 EDT 2016

Couldn't you get this behavior, though, by setting your attribute filter configuration for R&S category SPs to only release if the attribute was requested in metadata? And optionally if no requested attributes are in metadata for that SP?

It wouldn't handle the required/optional piece as I already pointed out, but it would at least honor requested attributes.


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, April 07, 2016 10:05 AM
To: Shib Users <users at shibboleth.net>
Subject: RE: Evolving Attribute Release Policies for campuses

> And... as currently packaged, the Shib IDP Consent screens will NOT act
> on any RequestedAttributes elements in the SPs metadata ? Can the
> Consent screens by configured in any way to act on those (eg if the site
> is NOT R&S ? )


> And... currently, the IDP does not make the isRequired values available
> to the Consent flow ?

Not in a practical way.

-- Scott

To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

More information about the users mailing list