Profile handler should use its getProfileId() method to obtain the communication...
authorputmanb <putmanb@ab3bd59b-922f-494d-bb5f-6f0a3c29deca>
Mon, 20 Jul 2009 23:33:01 +0000 (23:33 +0000)
committerputmanb <putmanb@ab3bd59b-922f-494d-bb5f-6f0a3c29deca>
Mon, 20 Jul 2009 23:33:01 +0000 (23:33 +0000)
Otherwise causes problems for subclassing.

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

src/main/java/edu/internet2/middleware/shibboleth/idp/profile/saml2/SSOProfileHandler.java

index 820cdff..63dd3ed 100644 (file)
@@ -167,7 +167,7 @@ public class SSOProfileHandler extends AbstractSAML2ProfileHandler {
 
             String relyingPartyId = requestContext.getInboundMessageIssuer();
             RelyingPartyConfiguration rpConfig = getRelyingPartyConfiguration(relyingPartyId);
-            ProfileConfiguration ssoConfig = rpConfig.getProfileConfiguration(SSOConfiguration.PROFILE_ID);
+            ProfileConfiguration ssoConfig = rpConfig.getProfileConfiguration(getProfileId());
             if (ssoConfig == null) {
                 String msg = MessageFormatter.format("SAML 2 SSO profile is not configured for relying party '{}'", requestContext.getInboundMessageIssuer());
                 log.warn(msg);
@@ -288,7 +288,7 @@ public class SSOProfileHandler extends AbstractSAML2ProfileHandler {
         requestContext.setMetadataProvider(getMetadataProvider());
         requestContext.setSecurityPolicyResolver(getSecurityPolicyResolver());
 
-        requestContext.setCommunicationProfileId(SSOConfiguration.PROFILE_ID);
+        requestContext.setCommunicationProfileId(getProfileId());
         requestContext.setInboundMessageTransport(inTransport);
         requestContext.setInboundSAMLProtocol(SAMLConstants.SAML20P_NS);
         requestContext.setPeerEntityRole(SPSSODescriptor.DEFAULT_ELEMENT_NAME);