[
https://issues.jenkins-ci.org/browse/JENKINS-13526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162371#comment-162371
]
dogfood commented on JENKINS-13526:
-----------------------------------
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[jenkins_ui-changes_branch
#26|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/26/]
[FIXED JENKINS-13526] use '@' prefix to force PAM to interpret the
user/group as a group (Revision db1b7eef1a9a67b5f08e73d349230e0cec5a485d)
Result = SUCCESS
Kohsuke Kawaguchi :
[db1b7eef1a9a67b5f08e73d349230e0cec5a485d|https://github.com/jenkinsci/jenkins/commit/db1b7eef1a9a67b5f08e73d349230e0cec5a485d]
Files :
* core/src/main/resources/hudson/security/PAMSecurityRealm/help.html
* changelog.html
* core/src/main/java/hudson/security/PAMSecurityRealm.java
> PAM security realm should have a way to differentiate users from groups
> -----------------------------------------------------------------------
>
> Key: JENKINS-13526
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13526
> Project: Jenkins
> Issue Type: Improvement
> Components: core, security
> Reporter: Rob Petti
>
> This is an issue that came up in the #jenkins irc channel.
> There is currently a limitation when using PAM with matrix based security. If
> a group's name matches that of a user, it cannot be used in the
> configuration, as it will always select the user instead of the group.
> I propose supporting a prefix, such as '@' that will explicitly identify the
> group/user as a group.
--
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
