...
- technical contact: for direct communication between InCommon participants regarding technical issues such as troubleshooting software, systems, or networking issues
- administrative contact: for direct communication between InCommon participants and by institutional users regarding non-technical issues such as attribute release policy, on-boarding issues, privacy, assurance certification and assurance qualifiers, etc.
- security contact: for direct communication between InCommon participants regarding security matters, especially for the purposes of Federated Security Incident Response
- support contact: for end-user technical support but may also handle questions from users regarding attribute release policy, user privacy, access issues relating to assurance, etc.
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
...
- in metadata.
- At least one security
...
- contact is REQUIRED in metadata.
| Tip |
|---|
Contact information should be role-based such as help_desk@example.org rather than individual such as janedoe@example.org. |
...