On 9/27/07, Lucas Rockwell <[EMAIL PROTECTED]> wrote: > > Mike, > > Thanks for the response. > > More below. > > On Sep 27, 2007, at 3:33 PM, Mike Kennedy wrote: > > > Lucas, > > > > We are currently just beginning work on this at our site. > > Unfortunately > > since we are just in the planning stages I can't give you more than > > what we > > plan to do. > > > > We created a new objectClass in our ldap directory that services > > entries > > will use. > > That is a good start. I assume you used something like > org.jasig.cas.services.RegisteredServiceImpl to determine all the > datatypes? > > I do not see these defined anywhere else (well, as "gets" in > org.jasig.cas.services.RegisteredService), unless I am missing > something.
The list of available/required attributes is on the RegisteredService interface (the exposed getters). > We are then going to implement the > > org.jasig.cas.services.ServiceRegistry, > > org.jasig.cas.services.ServiceRegistryManager and > > org.jasig.cas.services.ServiceRegistryReloader interfaces to use > > ldap via > > JNDI to do lookups as necessary on those services entries. > > How will you deal with the "id" attribute? Are you going to do like > in RegisteredServiceImpl where they use GenerationType.AUTO? > > I notice, too, that the DefaultServicesManagerImpl implements the > reload() method, however, does the CAS part of the Registered > Services require that the services be reloaded after a change, or > does it do a lookup for each new request? The DefaultServiceRegistryManagerImpl will by default cache values returned from the ServiceRegistryDao for faster performance. It exposes a reloadable method to refresh the cache. -Scott
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
