Admin tab visibility does not respect authentication via group membership

[jeffstewart@…]

Adding the TRAC_ADMIN permission to a group of users created using the steps in http://trac.edgewall.org/wiki/TracPermissions#PermissionGroups does not cause the Admin tab to appear when a member of that group authenticates.

[info@…]

same with my installation. some solutions?

[mgood]

First be sure you've enabled the plugin. You should also be sure to restart the Trac web server after installing a new plugin.

Are you saying it works when you add the TRAC_ADMIN permission to a specific user, but not with a group? If so can you provide the output of "trac-admin your-project permission list" and the names of users you've seen this with.

[swithin@…]

Output of "python trac-admin c:\svn\trac.db permission list > permissionoutput.txt"

[anonymous]

I ran the permission dump that mgood requested against Trac 0.9.4 after I saw the same error myself (in Trac 0.9.4) and found this ticket. See attached file called permissionoutput.txt. Note in there there is a user called jfrenia. When he was only assigned to the Administrator group, he didn't see the Admin tab. But as soon as I added the TRAC_ADMIN permission, he could see it. I'm not sure if you will want to use this test output since it came from 0.9.4 rather than 10.2, but if the problem always existed (even in earlier versions of Trac), it should be valid output.

[Noah Kantrowitz <coderanger@…>]

All group names should be lowercase. You have one called Administrator.

[sid]

That has caught a lot of people, and is documented here: TracPermissions#PermissionGroups

[mgood]

Yes, at the moment you can't have any uppercase letters in a group name. I had the impression that they simply couldn't be all uppercase, but based on the code that's not true. Is there a reason to prevent mixed-case group names? This should be fairly easy to fix.

[cboos]

So what do we do about this ticket and the possibility to have mixed-case group names. As we're working on the permissions for 0.11, it's probably a good time to decide about this.

[mgood]

Yeah, currently mixed case names are being considered as permissions rather than groups, so I think it makes sense to switch that around.

[mgood]

Done in r4958.