Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Contact information is expressed in series of <md:ContactPerson>
elements in SAML metadata. Note these rules when working with metadata registered in the Incommon Federation:
- Each
<md:EntityDescriptor>
element SHOULD contain at least four contacts. Each contact is expressed using the<md:ContactPerson>
element. Each should have XML attributescontactType="support"
,contactType="technical"
, andcontactType="administrative"
, plus a fourth<md:ContactPerson>
element with XML attributecontactType="other"
respectively. The element with the contactType="other" is the Security Contact, It carries an extra XML attribute indicating the contact is a security contact. See example below. - An entity MUST declare a technical contact (
contactType="technical"
). - An entity MUST declare an administrative contact (
contactType="administrative"
). - An entity MUST declare a security contact (
contactType="other"
; with an extended REFEDS metadata attribute ofcontactType="
http://refeds.org/metadata/contactType/security
".) - Each
<md:ContactPerson>
element MUST contain at least one<md:EmailAddress>
element. - If a contact is a non-person (such as a mailing list), the
<md:GivenName>
element MAY contain a title or label, and the<md:SurName>
element SHOULD be omitted. - If a contact is a real person, the
<md:GivenName>
and<md:SurName>
elements SHOULD reflect the person's real name.
|
See saml-metadata-contacts for information on how ContactPerson is used in InCommon metadata.
Get help
Can't find what you are looking for?
Button Hyperlink | ||||||||
---|---|---|---|---|---|---|---|---|
|