...
User consent at the IdP is not a panacea, but we do believe it is an important tool in the toolkit.
The vision, in practice
The situation we are seeking to enable, then, is as followsWe seek to enable the following scenario.
In addition to the information registered in metadata now, an SP admin registers information about the attributes their site requires (or would like to obtain) for login to proceed successfully. A . In addition, a user-meaningful name for the SP (e.g., "Bob's Excellent Article Database") is registered so that users don't have to decipher URLs when deciding who whether or not to release their information to (in fact, a major purpose of identifying SPs using metadata is to associate a site's name and description with its various and changing URLs). SPs might also register other meta-characteristics (e.g., "operated by university", "test site") that could be relevant to policy decisions. This information is published in InCommon 's metadata alongside the other SP information metadata that is there published today.
IdP admins install enhanced IdP software (Shibboleth or other products) that is able to consume that consumes the SP's requested attributes and other characteristics related elements from federation metadata and make it available to Federation metadata, making this new information available to the software's attribute release mechanisms. IdP admins also install user-consent mechanisms in their IdPs, and support them in their user community via documentation, help desk, etc. IdP institutions also develop attribute-management policies to take advantage of these new features.More importantly, IdP institutions develop attribute release policies that take advantage of the new user-consent mechanisms installed in their IdPs.
Now, when a user accesses Then, when a user goes to an SP for the first time, the attribute and consent machinery at the IdP comes into play. If the SP is in the IdP default policy categoryis satisfied, the IdP software determines the requested attributes and asks the user to consent to their release, storing the decision for next timelater use. If the user consents, attributes are released and the login succeeds (subject to SP access controls). If release to this SP requires a human policy decision, this event can start a workflow to alert the policy decision-makers.
Steps to making it happen
...