Change name of existing trust engine configuration element types, to disambiguate...
authorputmanb <putmanb@ab3bd59b-922f-494d-bb5f-6f0a3c29deca>
Tue, 15 Jan 2008 22:58:52 +0000 (22:58 +0000)
committerputmanb <putmanb@ab3bd59b-922f-494d-bb5f-6f0a3c29deca>
Tue, 15 Jan 2008 22:58:52 +0000 (22:58 +0000)
that they represent a specific type of trust engine + a specific type of resolver (metadata).
This is preparation for adding new trust engine configuration element types which aren't metadata-based.

git-svn-id: https://subversion.switch.ch/svn/shibboleth/java-idp/trunk@2574 ab3bd59b-922f-494d-bb5f-6f0a3c29deca

resources/conf/relying-party.xml

index 492f83e..131d359 100644 (file)
         secure.  Naturally some of these checks require the validation of the tokens evaluated by the trust 
         engines and so you'll see some rules that reference the declared trust engines.
     -->
-    <security:TrustEngine id="shibboleth.SignatureTrustEngine" xsi:type="security:ExplicitKeySignature"
+    <security:TrustEngine id="shibboleth.SignatureTrustEngine" xsi:type="security:MetadataExplicitKeySignature"
                           metadataProviderRef="ShibbolethMetadata" />
                           
-    <security:TrustEngine id="shibboleth.CredentialTrustEngine" xsi:type="security:ExplicitKey"
+    <security:TrustEngine id="shibboleth.CredentialTrustEngine" xsi:type="security:MetadataExplicitKey"
                           metadataProviderRef="ShibbolethMetadata" />
     
     <security:SecurityPolicy id="shibboleth.ShibbolethSSOSecurityPolicy" xsi:type="security:SecurityPolicyType">