Page tree

Versions Compared

Key

  • 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

ConditionLevelSignificanceReason
1

Signing certificate expired

Warnings on entity level

1-global1Currently implemented as a validator warning. To be confirmed by the SG.
2md:EmailAddress in md:ContactPerson element should start with mailto: prefix2-entity4This violates line 495 of https://docs.oasis-open.org/security/saml/v2.0/saml-metadata-2.0-os.pdf and should be considered an error!
3

SIRTFI attribute present and security contact found but no http://refeds.org/metadata/contactType/security contactType

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

SIRTFI attribute declared but no appropriate md:ContactPerson set

2-entity2SIRTFI specification error
5

shibmd:Scope with no regexp attribute

2-entity5https://wiki.shibboleth.net/confluence/display/SC/ShibMetaExt+V1.0 recommendation
6

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
2-entity
Since http://docs.oasis-open.org/security/saml/Post2.0/
saml
sstc-metadata-
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 http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-metadata-ui/v1.0/cs01/sstc-saml-metadata-ui-v1.0-cs01.pdf section 2.2.4 should be an errormdui:
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.
7

mdrpi:RegistrationPolicy not found

2-entity3eduGAIN SAML profile Section 3
8

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

2-entity

9mdui:UIInfo not found, no mdui:DisplayName and mdui:Description present3-role
eduGAIN SAML profile Section 3
10mdui:UIInfo with mdui:DisplayName found but mdui:Description not present3-role
eduGAIN SAML profile Section 3
11mdui:UIInfo found but mdui:DisplayName not present3-role
eduGAIN SAML profile Section 3
12mdui:UIInfo found but neither mdui:DisplayName nor mdui:Description present3-role
eduGAIN SAML profile Section 3
13mdui:UIInfo found but no mdui:Logo element3-role
eduGAIN SAML profile Section 3
14this SP does not provide requested attribute specification3-role
left from saml2int - should it be kept?
15Data Protection Code of Conduct declared but no mdui:PrivacyStatementURL found3-role
Violates the CoCo spec
16CoCo declared but md:RequestedAttribute element not found3-role
Violates the CoCo spec
17CoCo declared but mdui:PrivacyStatementURL and md:RequestedAttribute elements not found3-role
Violates 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