Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


This document specifies recommendations for upstream metadata produced by eduGAIN participants. Failure to comply with these recommendations will result . in a warning produced by the eduGAIN metadata validator using the eduGAIN SAML profile v2.

The table below lists currently implemented validator warnings, those recommendations are organised as a set of rules which may be easily verified by the eduGAIN metadata validator.

The rules marked red are actually specification errors and should be upgraded to validator errors (to be discussed within the eduGAIN SG)

Global warnings


Signing certificate expired

1-global1Currently implemented as a validator warning. To be confirmed by the SG.
Warnings on entity level
2md:EmailAddress in md:ContactPerson element should start with mailto: prefix2-entity4This violates line 495 of and should be considered an error!

SIRTFI attribute present and security contact found but no contactType

2-entity2SIRTFI specification error
assurance-certification entity attribute is defined,

SIRTFI attribute declared but no appropriate md:ContactPerson set

2-entity2SIRTFI specification error

shibmd:Scope with no regexp attribute

2-entity5 recommendation

mdattr:EntityAttributes placed in md:Extensions element of SPSSODescriptor/IDPSSODescriptor, expected in  md:Extensions element of EntityDescriptor

mdrpi:RegistrationPolicy not found

mdrpi:RegistrationInfo element defined more than once within a given md:Extensions element

This violates
rpi/v1.0/cs01/saml-metadata-rpi-v1.0-cs01.html section 2.1 therefore should be an error

mdui:PrivacyStatementURL does not start with http:// https://

Not a direct specification error, but probably should be considered as such?mdui:GeolocationHint should start with geo: prefixviolation of section 2.2.4 should be an error
attr.html does not define appearance of this element in places other then md:Extensions element of EntityDescriptor it is most likely that the condition is a result of a mistake.

mdrpi:RegistrationPolicy not found

2-entity3eduGAIN SAML profile Section 3

mdattr:EntityAttributes element contains saml:AttributeValue with leading/trailing whitespaces

mdattr:EntityAttributes element appears more than once within a given md:Extensions element 

Warnings on entity’s role level

9mdui:UIInfo found but mdui:DisplayName not present3-role3eduGAIN SAML profile Section 3
10mdui:UIInfo found but no mdui:Logo element3-role1eduGAIN SAML profile Section 3
11for SP: mdui:UIInfo not found, no mdui:DisplayName and mdui:Description present3-role3eduGAIN SAML profile Section 3
12for SP: mdui:UIInfo with mdui:DisplayName found but mdui:Description not present
eduGAIN SAML profile Section
mdui:UIInfo found but mdui:DisplayName not present
-role3eduGAIN SAML profile Section 3
13for SP: mdui:UIInfo found but neither mdui:DisplayName nor mdui:Description present
eduGAIN SAML profile Section
mdui:UIInfo found but no mdui:Logo element
-role3eduGAIN SAML profile Section 3
14this SP does not provide requested attribute specification3-role1left from saml2int - should it be kept?
15Data Protection Code of Conduct declared but no mdui:PrivacyStatementURL found3-role4Violates the CoCo spec
16CoCo declared but md:RequestedAttribute element not found3-role4Violates the CoCo spec
17CoCo declared but mdui:PrivacyStatementURL and md:RequestedAttribute elements not found3-role4Violates the CoCo spec

Global warnings

Some SP does not provide requested attribute specification– chyba można pominąć, bo pojawiają się te warningi na poziomie role

md:EntitiesDescriptor element does not contain the ID attribute which should be used in signature’s ds:Reference  bez sensu bo przecież ID musi być z powodu reference w podpisie

Some entities do not have an encryption certificate

Some SP entities do not have an encryption certificate

Some SP does not provide requested attribute specification to wszystko jest wymienione na poziomie role