Opened 18 years ago
Closed 14 years ago
#3179 closed enhancement (wontfix)
global login in multiproject site
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | 0.9.3 |
Severity: | normal | Keywords: | login session multipleprojects |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
we are using trac in a setup with multiple projects
each project has an url like http://trac.domain.tld/projectname/
the problem is that we have to login to each project sepereately. is there any way to realize a global session handling or point trac to use one specified database for the session handling so that when you login once you are logged in in all projects and can keep your settings all over the system.
Attachments (0)
Change History (7)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
i already did this. this is how it looks in my apache config
<LocationMatch "/[[:alnum:]]+/[a-zA-Z0-9\.\-\_]+/login"> AuthType Basic AuthName "trac" AuthUserFile /var/trac/auth Require valid-user </LocationMatch>
the problem is that you still need to click login all the time and that you need to define the settings.
is there no way to point all the projects to one projects login perhaps. in this way you would set it up in one projects and this would be something like the master for the other projects.
comment:3 by , 18 years ago
i came up with a workaround that cycles through all projects and adjusts the database. the problem is that i cannot set more then 50 cookies per domain which is the blocker now.
is there anyway i can patch the trac system so it will check for the same cookie within all projects?
comment:4 by , 18 years ago
Milestone: | → 1.0 |
---|
See also #4226, in particular comment 4.
- For the TracMultipleProjects/SingleEnvironment approach, single log for multiple projects will be for free.
- For the TracMultipleProjects/MultipleEnvironments approach (current one), one could think about using a parent/default environment for delegating the session and permission management.
comment:7 by , 14 years ago
Milestone: | triaging |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
This is implemented in the th:SharedCookieAuthPlugin, which makes use of the new [trac] auth_cookie_path
option (#8486).
You can assign the same HTTP realm to all the projects, so that the browser sends the appropriate credentials when the user moves from one project to another. This avoids to login on each project, but you'll have to define the settings (name, email address) for each project.