Quantcast

[JIRA] (JENKINS-15484) New permission controlling ability to configure your own User

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15484) New permission controlling ability to configure your own User

JIRA noreply@jenkins-ci.org
Issue Type: Improvement Improvement
Assignee: Jesse Glick
Components: core
Created: 11/Oct/12 2:45 PM
Description:

An administrator may want to block access to /me/configure, for example to prevent users from changing their own display names.

Currently this appears to be impossible, as User.doConfigSubmit calls User.checkPermission, not Jenkins.checkPermission, and User.getACL is implemented to give every user permission to configure himself, regardless of authorization strategy.

User.doConfigSubmit should additionally check some newly introduced global permission (such as User.SELF_CONFIGURE) which would be on by default for all (authenticated) users but could be explicitly disabled.

The tricky part is introducing such a permission and granting it by default, since new permissions are rejected by default, and this one should not be implied by any existing permission.

Project: Jenkins
Labels: security user configuration permissions
Priority: Major Major
Reporter: Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15484) New permission controlling ability to configure your own User

JIRA noreply@jenkins-ci.org
Jesse Glick commented on Improvement JENKINS-15484

Introduce permission in core, implied by ADMINISTER, disabled by default, called by User.getACL or User.doConfigSubmit only if enabled; then create a plugin which does nothing but enable the permission. Awkward but may work.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15484) New permission controlling ability to configure your own User

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Because of the compatibility issue, let's do it like how we did extended job configuration read permission — define the permission in core, deactived by default, and a custom plugin that enables it.

At the same time, we start remembering negative permissions in our authorization strategies so that new permissions like this can be added later more naturally in future versions.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Loading...