Note: Further work on this topic was done and a more complete technical proposal put together by the UCTrust SP Integration Workgroup.
DRAFT
Attachment (Added 4/20/2015): Federated Authentication Data Release Approval Processes v0.3.docx, this same proposal cast as a document for non-technical audiences.
...
- An aspiring UCTrust SP identifies the bundle of attributes it would like to obtain.
- The SP owner documents how it meets the usage criteria of the bundle.
- The SP owner's UCTrust campus rep reviews the proposal, and when satisfied, submits it to the UCTrust governance committee.
- If approved, UCTrust submits the request for the attribute to be added to the entity and notifies the UCTrust rep (who, if a different person, will have to contact the local InCommon Site Admin) to approve the attribute. NOTE: the actual technical mechanism used to convey "UCTrust approval" may differ from this depending on whether this specific functionality will be supported by InCommon.
This is still an early stage in developing this process, so we don't yet have details to propose regarding all of the above steps and what they mean. We're hoping to suss some of those things out through discussion.
...