> But, what seems simple in jetspeed1.3 seems > to > be spread over a lot of files in jetspeed1.4 .
Jetspeed Security Services have been re-designed from the ground up, outside of Turbine's security service. I doubt that just changing the Jetspeed Security Service information in the properties file to Turbine's LDAP service will work. I have 2 reasons why this won't work: 1. AFAIK, Turbine's LDAP security has never been complete. I know there has been some talk in recent weeks on the Turbine list about LDAP and security in general but I don't think any progress has been made due to apparent lack of interest. Someone correct me if I'm wrong. 2. I am almost positive that Turbine's LDAP security does not implement the correct security interfaces required by jetspeed security to just be "plugged in." Scott > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 08, 2002 2:19 AM > To: Jetspeed Users List > Subject: Re: jetspeed authentication using LDAP > > > We can change the SecurityService class to be used to LDAPSecurityService > and the User and UserManager classes to LDAPUser and LDAPUserManager in > org.apache.turbine.services.security.ldap package. This is supposed to be > just a property file change. But, what seems simple in jetspeed1.3 seems > to > be spread over a lot of files in jetspeed1.4 . And also, as you have said, > there is this TurbineAuthentication in jetspeed itself, instead of using > classes directly from Turbine. > Has anybody tried to use LDAP authentication in jetspeed1.4 by just > changing the property files to point to an LDAPSecurityService > > Regards, > Lavanya > > > > > Glen Carl > <carl@csc-mont To: Jetspeed Users List > <[EMAIL PROTECTED]> > erey.com> cc: > Subject: Re: jetspeed > authentication using LDAP > 10/02/02 11:15 > PM > Please respond > to "Jetspeed > Users List" > > > > > > > I am currently customizing > jetspeed/services/security/turbine/TurbineAuthentication.java > to send a SOAP message to a web service that interfaces with LDAP. Our > SOAP request contains username and password, and the SOAP response > returns a Success/Failure status code and some custom user information. > Using the SOAP web service allows us to keep our authentication > adaptable and independent of the portal and LDAP vendors. Has anyone > else attempted to authenticate via a SOAP web service? > > From what I understand from the Jetspeed security documentation, you do > not need to use the TurbineAuthentication. However, Turbine currently > fits well with Jetspeed, and this is why I am modifying > TurbineAuthentication.java as a start. I am interested in any other > Authentication implementations that the Jetspeed community feels will > replace Turbine. > > [EMAIL PROTECTED] wrote: > > Hi, > > I am a new user to jetspeed. Has anyone replaced the database based user > > authentication with LDAP based authentication? If so, can you please > throw > > some light on it? > > > > Regards, > > Lavanya > > > -- > To unsubscribe, e-mail: < > mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: < > mailto:[EMAIL PROTECTED]> > > > > > > -----------------------Disclaimer------------------------ > > The views of the author may not necessarily reflect those > of the Company. All liability is excluded to the extent > permitted by law for any claims arising as a result of the > use of this medium to transmit information by or to > IT Solutions (India) Pvt. Ltd. > > We have taken precautions to minimize the risk of > transmitting software viruses, but we advise you to > carry out your own virus checks on any attachment to > this message. We cannot accept liability for any loss or > damage caused by software viruses. > > ------------------------Disclaimer------------------------ > > > -- > To unsubscribe, e-mail: <mailto:jetspeed-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:jetspeed-user- > [EMAIL PROTECTED]>
