> an authentication class gets created. However, the Principal does not get > the attributes associated with it. The authentication class gets the > attributes.
You'll need to provide some evidence to support this claim. We make heavy use of SAML validation with attribute release and it works in every version we've tested, including the latest 3.5.1-RC1. > When the code runs this line "if > (!authentication.getPrincipal().getAttributes().isEmpty() || isRemembered) > ", and you haven't configured RememberMe, the attributes never get picked > up in the SAMLStatement that is create when "if > (!authentication.getPrincipal().getAttributes().isEmpty() || isRemembered) " > is executed. I changed the code to use "if > (!authentication.getAttributes().isEmpty() || isRemembered) " which > appearently worked That likely produces some data because both the authentication and principal can contain data. I'm fairly certain this is a case of a permission issue related to service management or a misconfigured attribute source. I reviewed your Spring context config and didn't see anything obvious, but there's a lot in there that is clearly specific to your environment. One possible issue could be the query to look up attributes in the LDAP is failing. I'd recommend turning up the org.jasig.services.persondir.support.ldap to DEBUG and reviewing logging output. Post relevant log excerpts (redacted as necessary) if you'd like a second set of eyeballs. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
