Hi, I just found this. http://www.mail-archive.com/[email protected]/msg05678.html
In my eyes the main problem is, that Turbine comes with its very own Security Domain Model. Which is wehy the Container Java Security Model, which provides that, does not apply to turbine apps. Kind regards Juergen -----Ursprüngliche Nachricht----- Von: Jeffrey D. Brekke [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 13. Dezember 2006 06:58 An: Turbine Users List Betreff: Single Sign On and Turbine Has anyone integrated a single sign on solution for multiple turbine web applications? We are considering using a single turbine applications, authenticating against active directory. When the user is logged in, throw the session id and username into a table. Then the other applications, using a customer session revalidation, check if the user is logged in as usual, if not, check if the id exists in the table and if so, create an authenticated user for use in that turbine app. But, how do we get the same cookie from one app into another? Are there any other ways to do sso with turbine in use? -- ===================================================================== Jeffrey D. Brekke [EMAIL PROTECTED] Wisconsin, USA [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.bloglines.com/blog/jbrekke [EMAIL PROTECTED] --------------------------------------------------------------------- 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]
