On 9/28/07, Lucas Rockwell <[EMAIL PROTECTED]> wrote: > > Scott, > As always, thanks for the information. So questions below. > > On Sep 28, 2007, at 5:02 AM, Scott Battaglia wrote: > > Lucas, > > Here's a quick description of the services package: > ServiceRegistryManager is the interface for the service layer. It has a > default implementation of DefaultServiceManagerImpl. > > > Does "manager" in this case mean it manages the services for both the CAS > server (logins and validation) and for the registry management console? I > assume both things interact with this service layer. >
The manager is the service layer that interacts with both the Authentication/Validation component (i.e. the CentralAuthenticationService) and the Services Management Interface. Let me know if you have other questions or comments. Hope that helps. -Scott DefaultServiceManagerImpl also implements ReloadableServiceManager. The > implementation caches values returned from the Repository for improved > performance and can be reloaded occasionally via the exposed > ReloadableServiceManager method. > > RegisteredServiceImpl is the default implementation of the > RegisteredService. Even if you are using another backend data store, you > should be able to use this implementation. > > ServiceRegistryDao controls the interaction between the data store and the > service layer. This is the layer that would communicate with LDAP. > > The RegisteredService interface should contain the list of attributes that > would need to be stored in the LDAP. > > If you get this working, please consider creating a JIRA issue and > donating the code to the CAS project! Let me know if you need more > information. > > > I certainly will. Perhaps Mike Kennedy and I can come up with something, > as I think we're thinking along the same lines with this. > > -lucas > > Thanks > -Scott > > On 9/27/07, Lucas Rockwell <[EMAIL PROTECTED]> wrote: > > > > 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 > > > > > > -- > -Scott Battaglia > > LinkedIn: http://www.linkedin.com/in/scottbattaglia > _______________________________________________ > 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 > > -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
