The SecurityService in Turbine was designed to work with different implementations. So far we have two: DBSecurityService based on Torque and LDAPSecurityService which works with an LDAP repository. A new implementation of the DBSecurityService is being developed which has a better design but still it relies on Torque. -- Humberto
------------------- > Hi > We are developing a commercial application based on Turbine, but we are > not using Torque. Right now we have reached a point where we need to start > developing our security module and looking through the documentation and > how-to's I realized that the current security service is heavily based on > Torque. Since we don't want to use Torque just because of the security > service, we have been thinking about creating our own Security Service > basing it on JAAS. > Since I think this has not been done yet, I looked through your dev > mailing list archive and found some discussions around this issue. Still, I > wasn't able to see if something is actually on dev process now. I also read > about JASF but it wasn't clear it is going to be integrated into Turbine as > the next Security Service or Security Manager (are these the same thing?). > But even if JASF gets into Turbine, is it JAAS based? Thanx... > > Rodrigo > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
