Hi Shi,

I think our requirements are a bit different. It looks like you are  
describing authentication (but correct me if I am wrong). We already  
use Kerberos for authentication, and then go to LDAP and get the  
user's numeric ID from the provided principal string (username). It  
is the numeric ID that CAS hands back to the application. We do this  
using a JAAS stack that we already had, so very little configuration  
in CAS was required for this.

What I am looking to do is put the service registry in LDAP instead  
of in memory or in a database.

Thanks.

-lucas

On Sep 28, 2007, at 1:20 AM, Shi Yusen wrote:

> Hi Lucas,
>
> I'm just starting the following:
>
> User           Applications          CAS              LDAP
> |   userid/passwd    |                |                |
> |--------req-------->|                |                |
> |                    |------req----->|                |
> |                    |                |  userid/basedn |
> |                    |                |-------req----->|
> |                    |                |     userdn     |
> |                    |                |<------res------|
> |                    |                |  userdn/passwd |
> |                    |                |-------req----->|
> |                    |                |<------res------|
> |                    |<------res------|                |
> |<-------res---------|                |                |
>
> If your requirement is similar, perhaps we can cooperate on this.
>
> Regards,
>
> Shi Yusen/Beijing Langhua Ltd.
>
>
> 在 2007-09-27四的 14:50 -0700,Lucas Rockwell写道:
>> Hi all,
>>
>> I would like to put the Service Registry information in our LDAP
>> server, but I am feeling a little lost.
>>
>> I see this page http://www.ja-sig.org/wiki/display/CASUM/Configuring
>> for configuring the backend as a database, but I don't think it is as
>> straight-forward for ldap, especially since we don't let applications
>> just create new schema objects on the fly (as it looks like that is
>> what the Hibernate code is doing for a database).
>>
>> It looks like InMemoryServiceRegistryDaoImpl just implements
>> ServiceRegistryDao, but even looking at those two things and all the
>> other classes in that package do not give me a clear picture about
>> how to do this with ldap.
>>
>> Also, there is CAS itself that has to interact with the Registry, as
>> well as the management "console", but perhaps all of that is done via
>> the one "serviceRegistryDao" bean in applicationContext.xml...
>>
>> Any pointers to get me started would be great.
>>
>> Of course, I'll gladly put the solution on the wiki.
>>
>> Thanks!
>>
>> -lucas
>> _______________________________________________
>> 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

_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to