Opened 10 years ago
Closed 7 years ago
#12014 closed enhancement (fixed)
Move away from using TRAC_ADMIN
Reported by: | Keluri | Owned by: | Jun Omae |
---|---|---|---|
Priority: | normal | Component: | TracWorkflowAdminPlugin |
Severity: | normal | Keywords: | permissions |
Cc: | Trac Release: |
Description
I'd like to request that this plugin move away from using the rather vague 'TRAC_ADMIN' permission to something more specific, such as a custom 'WORKFLOW_ADMIN' permission.
I maintain a Trac installation where there's a group of users who have the ability to change project settings (for things like tickets, timelines, and the wiki), but not core settings (such as logging and user permissions). When installing this plugin, I had to modify the main class in web_ui.py to use a custom permission.
Attachments (0)
Change History (6)
comment:1 follow-up: 5 Changed 10 years ago by
comment:2 follow-up: 3 Changed 10 years ago by
I think it is a good choice to not add more permissions. Anyone wanting more fine-grained access control can use TracFineGrainedPermissions.
comment:3 Changed 10 years ago by
Replying to rjollos:
I think it is a good choice to not add more permissions. Anyone wanting more fine-grained access control can use TracFineGrainedPermissions.
After closer look, some modifications appear to be needed to support TracFineGrainedPermissions: tracworkflowadminplugin/0.12/tracworkflowadmin/web_ui.py@14210:129,134#L126. The changes needed are similar to comment:1:ticket:11826.
comment:5 Changed 7 years ago by
Replying to Jun Omae:
However, changing
TRAC_ADMIN
toTICKET_ADMIN
is okay to me.
Using TICKET_ADMIN
sounds good to me.
I don't want to add a new permission. However, changing
TRAC_ADMIN
toTICKET_ADMIN
is okay to me.