On Friday, November 27, 2015 at 1:16:02 PM UTC-8, olemis wrote: > > I do find it useful . I'll take a look and try to adapt this to deploy > onto my environments . > > -- > Regards, > > Olemis - @olemislc >
Thanks for testing. It looks like the feature implementation in AccountManagerPlugin is better than SharedCookieAuthPlugin, so credit to Steffen on that. AccountManagerPlugin sets the cookie in every environment, which looks like it will be more robust. SharedCookieAuthPlugin only sets the cookie in the authenticating environment and deletes the expired cookie to avoid other environment logging out the user. I couldn't see any other way to work around the issue of other environments expiring the cookie. Setting the cookie in every environment is also better because it doesn't have a minor issue that is seen with SharedCookieAuth. Say you have two environments and log into env1. You'll then be authenticated in env2, but if you logout of either environment and then login to env2 you'll be forced to enter credentials again. As a next step I'm hoping to make AccountManagerPlugin's implementation a standard feature of Trac, for inclusion in Trac 1.2. - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Users" 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/trac-users. For more options, visit https://groups.google.com/d/optout.
