[ 
https://issues.jenkins-ci.org/browse/JENKINS-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162680#comment-162680
 ] 

Adam Guja commented on JENKINS-4905:
------------------------------------

bumping, because it's a very good idea I'm looking for
                
> Auto-generate access permissions for auto-created users.
> --------------------------------------------------------
>
>                 Key: JENKINS-4905
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-4905
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: current
>         Environment: Platform: All, OS: All
>            Reporter: awb
>
> When using Hudson's own database for access control, it would be useful to
> auto-generate access permissions for users that have been auto-created.
> When a committer gets email notification about a broken build, they would like
> to be able to look at the Hudson logs. However, on an externally accessible
> Hudson server, it is desirable to use matrix-based authorization and to 
> disallow
> users to sign up. A small number of users can easily be given read permissions
> manually, but an automated process would greatly help, especially as new 
> people
> start to commit.
> In the case of LDAP-based authorization, groups of users can be created for 
> this
> purpose, but Hudson does not support this for its own database. It may be
> necessary to implement a general group concept for Hudson's access control
> database or (for purposes of this request) simply create a new special user
> "autocreated".
> Those newly created users should get an auto-generated password in email. 
> Since
> people tend to misplace those emails, it may make sense to send it not when 
> the
> user gets first created, but when the first broken build notification goes out
> (or both). A forced password reset upon first login may also be useful.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to