| Table of Contents | ||
|---|---|---|
|
Contact Information in Metadata
The principal use of contact information in metadata is to enable effective communication between Federation participants, especially when systems fail, when users encounter problems, or when a security incident occurs.
...
All are important in different scenarios, and participants are encouraged to provide at least one of each type. At least one technical contact is REQUIRED in metadata. At least one administrative contact is REQUIRED as well.
CCC Contacts Registered with InCommon
| Type | Description | Registered CCC Contact | Corresponding Person |
|---|---|---|---|
| Technical | technical issues such as troubleshooting software, systems, or networking issues | ? Should this be a Unicon person? Mike Grady ? | |
| Administrative | non-technical issues such as attribute release policy, on-boarding issues, privacy, assurance certification and assurance qualifiers, etc. | Tim Calhoon, CCCTC Director | |
| Security | security matters, especially for the purposes of Federated Security Incident Response | Jeff Holden, CISO, jholden@ccctechcenter.org | |
| Support | end-user technical support but may also handle questions from users regarding attribute release policy, user privacy, access issues relating to assurance, etc. | Matt Schroeder, Systems Engineer, mschroeder@ccctechcenter.org |
...
| Note |
|---|
| Contact information should be role-based such as help_desk@example.org rather than individual such as janedoe@example.org. |
User Scenarios
| Info |
|---|
| This information was taken directly from InCommon website: Contacts in Metadata |
...
Reliable contact information in metadata will enable workflows and scenarios such as those described above.
Technical Details
Here is an example of an appropriate set of <md:ContactPerson> elements in metadata:
...