Thanks for the clarification Scott. I finally got it.

Parker

On Thu, Feb 5, 2009 at 11:39 AM, Scott Battaglia
<[email protected]>wrote:

> Parker,
>
> As you said you should be able to use this:
>
> https://www.ja-sig.org/svn/cas3/trunk/cas-server-support-ldap/src/main/java/org/jasig/cas/authentication/principal/CredentialsToLDAPAttributePrincipalResolver.java
>
> You'll need to inject a CredentialsToPrincipalResolver that can take the
> provided credentials (UsernamePasswordCredentials for example) and return
> some form of Principal of that.  Then the
> CredentailsToLDAPAttributePrincipalResolver would look that up in LDAP and
> then it would call the appropriate AttributeRepository to look up the
> attributes.
>
> So you'll ned to configure CredentialsToAttributePrincipalResolver with the
> following:
> *Context Source to contact LDAP
> * CredentialToPrincipalResolver to take the original credential and provide
> a principal that can be looked up in LDAP
> * AttributeRepository that checks the appropriate attribute repository.
>
> -Scott
>
> -Scott Battaglia
> PGP Public Key Id: 0x383733AA
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>
>
> On Wed, Feb 4, 2009 at 5:41 PM, Parker Grimes <[email protected]> wrote:
>
>> So am I on the right track with this? I am thinking I need to implement my
>> own CredentialsToPrincipalResolver that builds the Principal object with the
>> LDAP username as the Principal id and populates the attribute map from my
>> database attributeRepository. Is that right? Or is there an existing
>> implementation of CredentialsToPrincipalResolver that I overlooked that will
>> do this?
>>
>> Thanks,
>> Parker
>>
>>
>>
>> On Fri, Jan 30, 2009 at 12:14 PM, Parker Grimes <[email protected]> wrote:
>>
>>> I thought so. I just couldn't find any documentation or examples of
>>> anybody else doing it. I am missing something and I am just not quite sure
>>> what.
>>>
>>> One thing I am unclear about is the credentialsToPrincipalResolvers.
>>> According to the documentation at
>>> http://www.ja-sig.org/wiki/display/CASUM/Attributes, which is specific
>>> to pulling attributes from LDAP, there is a
>>> CredentialsToLDAPAttributePrincipalResolver that gets the
>>> attributeRepository bean injected into it. What would the setup look like in
>>> this case where the user is authenticated against LDAP and the
>>> attributeRepository is pulling attributes from a database?
>>>
>>> Parker
>>>
>>>
>>> On Thu, Jan 29, 2009 at 4:43 PM, Scott Battaglia <
>>> [email protected]> wrote:
>>>
>>>> It should work fine.
>>>>
>>>> -Scott
>>>>
>>>> -Scott Battaglia
>>>> PGP Public Key Id: 0x383733AA
>>>> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>>>>
>>>>
>>>> On Thu, Jan 29, 2009 at 6:04 PM, Parker Grimes <[email protected]> wrote:
>>>>
>>>>> Is it possible to authenticate via LDAP and pull attributes from a
>>>>> database?
>>>>>
>>>>> For instance, use
>>>>> org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler as the
>>>>> authentication handler and use
>>>>> org.jasig.services.persondir.support.jdbc.SingleRowJdbcPersonAttributeDao
>>>>> for the attributeRepository?
>>>>>
>>>>> Thanks,
>>>>> Parker
>>>>>
>>>>> _______________________________________________
>>>>> Yale CAS mailing list
>>>>> [email protected]
>>>>> http://tp.its.yale.edu/mailman/listinfo/cas
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Yale CAS mailing list
>>>> [email protected]
>>>> http://tp.its.yale.edu/mailman/listinfo/cas
>>>>
>>>>
>>>
>> --
>> 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-user
>>
>>
> --
> 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-user
>
>

-- 
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-user

Reply via email to