-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove the fixup code for @use-less KeyDescriptor elements out of the…
… (registrar) import transform and add it instead to each of the four publication flow transforms. Similarly, remove the check for this case out of the check_shibboleth ruleset into its own check_fixups ruleset, and impose that on all of the publication flows through a new CHECK.publishable macro. There is no net effect of this for currently registered metadata. New registration may have @use-less KeyDescriptors, however, which will now be retainin their entity fragment files but still fixed up in the publication flows. Metadata imported from other sources may also now have @use-less KeyDescriptor elements without that being flagged as an issue as long as the fixup is applied at some time before publication.
- Loading branch information
Showing
8 changed files
with
125 additions
and
37 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,49 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <!-- | ||
| check_fixups.xsl | ||
| This checking ruleset verifies that certain fixups have been performed on the | ||
| metadata before it is published. | ||
| Author: Ian A. Young <ian@iay.org.uk> | ||
| --> | ||
| <xsl:stylesheet version="1.0" | ||
| xmlns:xsl="http://www.w3.org/1999/XSL/Transform" | ||
| xmlns:ds="http://www.w3.org/2000/09/xmldsig#" | ||
| xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" | ||
| xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" | ||
| xmlns:shibmd="urn:mace:shibboleth:metadata:1.0" | ||
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
| xmlns:idpdisc="urn:oasis:names:tc:SAML:profiles:SSO:idp-discovery-protocol" | ||
| xmlns="urn:oasis:names:tc:SAML:2.0:metadata"> | ||
|
|
||
| <!-- | ||
| Common support functions. | ||
| --> | ||
| <xsl:import href="check_framework.xsl"/> | ||
|
|
||
|
|
||
| <!-- | ||
| Checks for an IdP whose KeyDescriptor elements do not include a @use attribute. | ||
| This causes problems with the Shibboleth 1.3 SP prior to V1.3.1, which | ||
| interprets this as "no use permitted" rather than "either signing or encryption use | ||
| permitted". | ||
| Two checks are required, one for each of the IdP role descriptors. | ||
| --> | ||
|
|
||
| <xsl:template match="md:IDPSSODescriptor/md:KeyDescriptor[not(@use)]"> | ||
| <xsl:call-template name="fatal"> | ||
| <xsl:with-param name="m">IdP SSO KeyDescriptor lacking @use</xsl:with-param> | ||
| </xsl:call-template> | ||
| </xsl:template> | ||
|
|
||
| <xsl:template match="md:AttributeAuthorityDescriptor/md:KeyDescriptor[not(@use)]"> | ||
| <xsl:call-template name="fatal"> | ||
| <xsl:with-param name="m">IdP AA KeyDescriptor lacking @use</xsl:with-param> | ||
| </xsl:call-template> | ||
| </xsl:template> | ||
|
|
||
| </xsl:stylesheet> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters