New metadata validation requirements based on the federation Technical Profile 1.0.0 are being enforced in Federationsadmin. |
Section | Title | Applies to |
---|---|---|
2.1.3 | errorURL | Identity Providers (IdPs) |
2.1.6 | SAML certificates (signing) | Identity Providers |
3.1.4 | SAML certificates (encryption) | Service Providers (SPs) |
3.1.6 | RequestedAttributes | Service Providers |
errorURL
(IdP)Implemented: X May 2025
Requirement:
An Identity Provider MUST include an errorURL
element in its metadata.
“A Relying Party may use the errorURL of an Identity Provider to assist users in resolving login issues.”
IdPs SHOULD follow the SAML V2.0 Metadata Deployment Profile for errorURL.
Example:
xml <IDPSSODescriptor ...> <errorURL>https://idp.example.org/login-error</errorURL> </IDPSSODescriptor>
Action: Ensure your IdP metadata contains a reachable errorURL
.
Implemented: X May 2025
Requirement:
An Identity Provider MUST include at least one signing certificate.
“A KeyDescriptor element with no
use
attribute or one set tosigning
.”
Example:
xml <KeyDescriptor use="signing"> <KeyInfo> <X509Data> <X509Certificate>MIID...snip...</X509Certificate> </X509Data> </KeyInfo> </KeyDescriptor>
Action: Verify that a valid signing certificate is present in your metadata.
Implemented: X May 2025
Requirement:
A Service Provider MUST include at least one encryption certificate.
“A KeyDescriptor element with no
use
attribute or one set toencryption
.”
Example:
xml <KeyDescriptor use="encryption"> <KeyInfo> <X509Data> <X509Certificate>MIIF...snip...</X509Certificate> </X509Data> </KeyInfo> </KeyDescriptor>
Action: Ensure your SP metadata includes a valid encryption certificate.
Implemented: X May 2025
Requirement:
AttributeConsumingService
AttributeConsumingService
must have:ServiceName
(with xml:lang
)ServiceDescription
(with xml:lang
)RequestedAttribute
Each RequestedAttribute
must include:
Name
from the attribute profileFriendlyName
matching the same profileNameFormat
= urn:oasis:names:tc:SAML:2.0:attrname-format:uri
Example:
xml <AttributeConsumingService index="1"> <ServiceName xml:lang="en">Demo Service</ServiceName> <ServiceDescription xml:lang="en">Used for testing login functionality</ServiceDescription> <RequestedAttribute Name="urn:oid:1.2.752.29.4.13" FriendlyName="norEduPersonNIN" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri" /> </AttributeConsumingService>
Action: Add RequestedAttribute
definitions that match the federation profile. Remember to use xml:lang
for language tagging.
The validator enforces these rules only when metadata is uploaded or updated. Existing metadata is unaffected unless resubmitted.
For validation help, you can: