<meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I also experienced not Exception’s being thrown or errors logged.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The Attributes defined in attribute-resolver using SAML2String were simply being ignored when Shibboleth config was loaded.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So at the time SAML Assertion was being built the attributes were never being added.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>No, you are using a different version of Spring then me, I was on 3.0.5 you are using 3.2. Perhaps this was identified at a defect in the framework and addressed.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>To me the logic in Spring did not make any sense.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:green'>Matt Zmuda</span></b><b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'> </span></b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>|<b> </b></span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>IT Solutions Developer<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>DCTS Online Channels - Authentication and Security - CIP/ESR<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Brian Reindel [via Shibboleth] [mailto:<a href="/user/SendEmail.jtp?type=node&node=7589118&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>] <br><b>Sent:</b> Friday, August 02, 2013 8:43 PM<br><b>To:</b> Zmuda, Matthew R<br><b>Subject:</b> Re: Is IDP tied to specific spring version?<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I've successfully upgraded the IdP WAR to use Spring 3.2.x, and I have <br>not experienced any problems (yet). I have attributes that get passed <br>that use the SAML2String encoder, and no exceptions are thrown. <br>Everything appears to be working as it should. <br><br>On Tue, Jul 30, 2013 at 8:33 AM, avalanche333 <<a href="/user/SendEmail.jtp?type=node&node=7589057&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>> wrote: <o:p></o:p></p><div><p class=MsoNormal><div class='shrinkable-quote'><br>> For the record in-case there is plans to upgrade shibboleth to Spring 3.0.x <br>> the issue is <br>> thatedu.internet2.middleware.shibboleth.common.config.attribute.encoding.SAML2StringAttributeEncoderBeanDefinitionParser <br>> forces you to set an attribute "name". This name value ultimately gets <br>> registered in the org.springframework.core.SimpleAliasRegistry - aliasMap. <br>> However its the base class that actually uses the name so I suppose this <br>> would impact anything that extends <br>> edu.internet2.middleware.shibboleth.common.config.attribute.encoding.BaseAttributeEncoderBeanDefinitionParser <br>> and uses the name attribute. <br>> <br>> So at startup when the beans get loaded the AttributeEncoders defined in <br>> attribute-resolver that use type SAML2String (or anything that extends <br>> resolver:BaseAttributeEncoderType) with name attribute set would be ignored <br>> because Spring 3.0 had a change in the way it loads beans to get the name <br>> set and register it into the aliasMap. Once that name is in the alias map <br>> there is a check in <br>> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanNamesForType <br>> to only load beans with a name that is NOT found in the aliasMap. <br>> <br>> Spring 2.5.x does not have an issue because Spring does not add the name to <br>> the alias map. <br>> <br>> The call that triggers all this loading from shibboleth is in: <br>> <br>> edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver.onNewContextCreated(ApplicationContext <br>> newServiceContext) throws ServiceException <br>> <br>> beanNames = <br>> newServiceContext.getBeanNamesForType(AttributeDefinition.class); <br>> <br>> <br>> <br>> -- <br>> View this message in context: <a href="" target="_top" rel="nofollow" link="external">click here</a>.<br><a href="http://shibboleth.1660669.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml" target="_top" rel="nofollow" link="external"><span style='font-size:7.0pt;font-family:"Times New Roman","serif"'>NAML</span></a> <o:p></o:p></span></p></div></div><p><FONT FACE="Arial" style="font-size:8pt;"><br />
NOTICE: Confidential message which may be privileged. Unauthorized use/disclosure prohibited. If received in error, please go to www.td.com/legal for instructions.<br />
AVIS : Message confidentiel dont le contenu peut être privilégié. Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière d'aller au www.td.com/francais/avis_juridique pour des instructions.</FONT></p>
<br/><hr align="left" width="300" />
View this message in context: <a href="http://shibboleth.1660669.n2.nabble.com/Is-IDP-tied-to-specific-spring-version-tp7588771p7589118.html">RE: Is IDP tied to specific spring version?</a><br/>
Sent from the <a href="http://shibboleth.1660669.n2.nabble.com/Shibboleth-Users-f1660767.html">Shibboleth - Users mailing list archive</a> at Nabble.com.<br/>