The LDAPSecurityService is based on the org.apache.turbine.services.security.BaseSecurityService. It works almost in the same way as the the DBSecurityService works but it goes to an LDAP server instead of going to a DB. The implication is that if jetspeed already uses DBSecurityService, it should work with the LDAPSecurityService almost transparently.
I haven't had a chance to take a look at jetspeed or its security implementation so I am unable to comment on that. (yet) -- Humberto -----Original Message----- From: Ender KILICOGLU [mailto:[EMAIL PROTECTED]] Sent: Friday, January 10, 2003 3:40 AM To: 'Turbine Developers List' Subject: RE: LDAP service Yes sure I seen your modification and I think its an effort to make run older LDAP security codes. After reviewing your code I send my first mail. If you look cvs repo for jetspeed you will see two different services: one for backend and second is security implementation (for only Jetspeed not turbine ) which depend on LDAP backend. It s my idea but your implementation style is a bottle neck and never can be used for production area which do not use any pooling or object modeling like turbine. LDAP backend has some handicaps such as masterdn lookup (no object binding), also you need 1.4 for intelligent pooling, jetspeed version can only connect to one server. (this behaviour modified but not commited) Ender -----Original Message----- From: Humberto Hernandez Torres [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 6:08 PM To: Turbine Developers List Subject: RE: LDAP service I am sorry but I don't quite understand the message. I have been working in the implementation of LDAPSecurityService for Turbine and I may be able to help you if you want to use it from JetSpeed. You will need to use the latest development version turbine-2.3-dev -- Humberto -----Original Message----- From: Ender KILICOGLU [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 2:41 AM To: [EMAIL PROTECTED] Subject: LDAP service Hi all May be you heard jetspeed has a LDAP service which is used to provide security values but Its only a backend used same as a DB services. I think it will be very usefull if embedded to base Turbine. If somebody interested contact me. Ender -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
