Evolving Attribute Release Policies for campuses

[Steven Carmody]

Quick question about Consent support in the latest Shib IDP:

I'm guessing that if the requesting SP has an R&S tag, then a site would 
likely configure a release policy to release the full bundle. If the 
site has configured Consent in conjunction with R&S, then the user would 
be presented with a screen showing all the attributes in the bundle, and 
could indicate YES/NO.

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 ?

thanks !