The context isn't quite clear here, and also it's not clear what
problem you're having and how similar it is to the problem from this
thread.  But it makes me think of this, from my config:

    <bean id="authenticationManager" 
class="org.jasig.cas.authentication.PolicyBasedAuthenticationManager">
        <constructor-arg>
            <map>
                <!--
                   | IMPORTANT
                   | Every handler requires a unique name.
                   | If more than one instance of the same handler class is 
configured, you must explicitly
                   | set its name to something other than its default name 
(typically the simple class name).
                   -->
                <entry key-ref="ldapAuthenticationHandler" value="#{ null }" />
                <!-- <entry key-ref="ldapAuthenticationHandler" 
value-ref="usernamePasswordCredentialsResolver" /> -->
                <!-- <entry key-ref="primaryAuthenticationHandler" 
value-ref="primaryPrincipalResolver" /> -->
            </map>
        </constructor-arg>

I was having a problem with LDAP attributes not coming through, and I
fixed it by changing the value to null, as you can see in the above --
compare the first entry with what was there before, as shown in the
following commented-out line.

Hope this helps.

Milt Epstein
Applications Developer
Graduate School of Library and Information Science (GSLIS)
University of Illinois at Urbana-Champaign (UIUC)
mepst...@illinois.edu


On Mon, 12 Jan 2015, Aaron Spike wrote:

> 
> 
> On Wednesday, September 3, 2014 at 7:07:29 AM UTC-5, Marvin Addison wrote:
> >
> > > Nope, all that does is cause the attributes to have empty values in 
> > them: 
> >
> > Ok, I did a little code review and have a suggestion. The trigger to 
> > resolve attributes from a principal resolver is the definition of a 
> > PrincipalResolver component in the value side of 
> > PolicyBasedAuthenticationManager#handlerResolverMap. So keep your 
> > attributeRepository bean but don't wire it into your 
> > PolicyBasedAuthenticationManager bean. Let me know whether that fixes 
> > your problem. 
> >
> 
> From what I can understand of this thread, the configuration described 
> above could solve my current problem. Unfortunatly I don't know how to act 
> on the advice given. Can anyone provide an example of the appropriately 
> configured beans?
> 
> Aaron Spike 
> 
> -- 
> This electronic communication, including any attached documents, may 
> contain confidential and/or legally privileged information that is intended 
> only for use by the recipient(s) named above. If you have received this 
> communication in error, please notify the sender immediately and delete the 
> communication and any attachments. Views expressed by the author do not 
> necessarily represent those of Martin Luther College.
> 
> -- 
> You are currently subscribed to cas-user@lists.jasig.org as: 
> mepst...@illinois.edu
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-user

-- 
You are currently subscribed to cas-user@lists.jasig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to