...
A secondary function is to support user interfaces (UIs) but much of the contact information displayed by an identity provider or service provider (for example on error, discovery, login, or consent pages) is self-owned and therefore known by the presenting site. A notable exception is an identity provider contact suitable for brokering attribute release changes when users encounter failures accessing services because the Requested Attributes are not released to SPs.
CCC Contacts Registered with InCommon
Below are the four types of contacts required in Federation metadata and the CCC Contacts that align to them:
...
:
...
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.
...
| Type | Description | Registered CCC Contact | Corresponding Person |
|---|---|---|---|
| Technical | technical issues such as troubleshooting software, systems, or networking issues | Matt Schroeder, Systems Engineer | |
| Administrative | non-technical issues such as attribute release policy, on-boarding issues, privacy, assurance certification and assurance qualifiers, etc. | sso_admincontact@ccctechcenter.org | Lou Delzompo, CTO |
| Security | security matters, especially for the purposes of Federated Security Incident Response | sso_securitycontact@ccctechcenter.org | Jeff Holden, CISO |
| Support | end-user technical support but may also handle questions from users regarding attribute release policy, user privacy, access issues relating to assurance, etc. | sso_supportcontact@ccctechcenter.org | David Albrecht, Senior Systems Engineer, dalbrecht@ccctechcenter.org |
...