Share authentication among Trac-powered projects

[gustavo@…]

Hello.

I have several Trac-powered projects in ​http://tracker.gnulinuxmatters.org/ and I'd like them to share the authentication, this is, if someone logs in to ​http://tracker.gnulinuxmatters.org/ggl/, then s/he can automatically access other projects like ​http://tracker.gnulinuxmatters.org/tds/, ​http://tracker.gnulinuxmatters.org/fsgl/...

Technically, for this to work, one should only modify the cookie path of trac_db_auth, however, I'm not a Python developer, so I'm unable to give you a patch.

It would be great if you could make a cookie_basepath option inside dbauth in the Trac config file. A cookie_domain would also come in handy, in my opinion.

If you decide not to implement this feature, could you please tell me how to work around this?

Thanks in advance.

Cheers.

[Noah Kantrowitz]

It is worth noting that TracForge? already implements this in a generic way. As long as DBAuth uses the same cookie as the normal Trac login system, you can just use that.

[gustavo@…]

Thanks for the answer, coderanger!

TracForge looks very promising, but it's still experimental and I cannot afford breaking anything on that server.

Cheers.

[Noah Kantrowitz]

The authentication linking component is quite stable, and can be used without touching the more unstable bits in tracforge.admin. Just enable tracforge.linker.auth.* on your client envs, and make sure you set the master path as mentioned in the wiki page.

[anonymous]

Replying to coderanger:

The authentication linking component is quite stable, and can be used without touching the more unstable bits in tracforge.admin. Just enable tracforge.linker.auth.* on your client envs, and make sure you set the master path as mentioned in the wiki page.

Thanks! Then I'll give it a try!

[Ryan J Ollos]

Closing tickets for a deprecated plugin.