Edgewall Software
Modify

Opened 13 years ago

Last modified 4 years ago

#4226 new enhancement

tracd: access control for list of projects

Reported by: anonymous Owned by:
Priority: normal Milestone: unscheduled
Component: web frontend/tracd Version: 0.10.2
Severity: normal Keywords: security authentication
Cc: Branch:
Release Notes:
API Changes:

Description

I have tracd running with a few projects. When you go to http://host:port/, there is a list of "Available Projects". I would like to restrict access to this page, by something like .htaccess/.htpasswd in apache. Is this possible?

Attachments (0)

Change History (7)

comment:1 by Noah Kantrowitz (coderanger) <coderanger@…>, 13 years ago

Not really. You can essentially disable it by providing a new, blank template for that page (see TracInterfaceCustomization for how).

comment:2 by Emmanuel Blot, 13 years ago

Keywords: security authentication added; tracd htaccess htdigest access control password removed

(applying TracTicketTriage rules)

comment:3 by marcin at brzezinski dot net, 13 years ago

I'd like the same thing, since my different sets of users are interested in different projects, so a static HTML page wouldn't solve that either ;(

My clients which have multiple projects like to switch from one to other using the projects list screen, but I don't necessarily want them to see all the other projects we work on.

in reply to:  3 comment:4 by Christian Boos, 13 years ago

Milestone: 1.0

Replying to marcin at brzezinski dot net:

I'd like the same thing, since my different sets of users are interested in different projects, so a static HTML page wouldn't solve that either ;(

This is slightly more complex, as instead of an all or nothing access, you're wanting to check access to each env in turn. That might involve having to open each environment in turn for such a request. That's eventually doable if the environments are not cached afterwards.

Anyway, the support for multiple project done this way will probably remain weak, that's why we're favoring the TracMultipleProjects/SingleEnvironment approach. There, having such a dynamic list of projects per user would be easily doable (and probably a required feature).

Back to the TracMultipleProjects/MultipleEnvironments case, one alternative solution would be to have a default environment that could be used for checking the PROJECT_VIEW permission. That default environment could be easily set by using the TRAC_ENV_PARENT_DIR and TRAC_ENV_DIR parameters at the same time.

comment:5 by Christian Boos, 10 years ago

Milestone: 1.0unscheduled

Milestone 1.0 deleted

comment:6 by Christian Boos, 9 years ago

Milestone: triagingunscheduled

comment:7 by Ryan J Ollos, 4 years ago

Owner: Jonas Borgström removed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.