If your applications are being used by internal clients who are already logged in via LDAP or windows AD, then it is a nice feature to pass that information to your TG app so they do not have to log in again. You can also manage groups/permissions globally using the LDAP/AD interface rather than the TG admin for the application.
If your application is only used by external clients, then you only need the TG auth. Have you checked out Allura <https://forge-allura.apache.org/docs/installation.html#using-ldap> which uses LDAP for example code?. On Thursday, February 5, 2015 at 2:57:12 AM UTC-6, Luca Verardi wrote: > > On second thought, LDAP might not be the best solution to my problem. > Maybe a TG2 app acting as a SSO to multiple TurboGears apps? > Thing is, I have no idea where to begin? I've read the docs, but I'm still > struggling. > > Il giorno giovedì 5 febbraio 2015 01:56:33 UTC+1, Stuart Zurcher ha > scritto: >> >> I'm curious what others do with LDAP or Windows AD. >> >> At my work, we have a single login app that verifies the login and sets a >> cookie with the id, permissions and groups, etc. Then the other apps use >> the cookie for authentication rather than each application having a login >> page and verification. >> >> What are others doing, and what are your thoughts on the subject? >> > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/d/optout.
