If I recall correctly (and I probably don't :) ) users get added based off
of SCM users of the jobs you are running. If James Young had a SCM entry
with jamesyoung, I wonder if Jenkins is matching the JamesYoung entry
(possibly due to the Windows case insensitivity as I think users are stored
@ the
Daniel is on to something regarding matching case. When it comes to case
[in]sensitivity, however, the behavior of Jenkins is a bit of a mystery.
When I was using a Linux machine as the Jenkins server, there was no
mystery. A mixed case login ID was always treated with case sensitivity.
Now t
Update: The user that I re-added had Administrator capability for a while,
but now that user no longer has Administrator rights. The check-boxes in
Matrix Based Security have not been changed.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
Make sure the user name is in the correct, same case (e.g. lowercase, or first
letter uppercase, etc.) everywhere. In the user DB/LDAP/..., when logging in,
in the security configuration.
On 28.01.2015, at 17:33, Steve K wrote:
> As a workaround, I removed one of the users who was supposed to
As a workaround, I removed one of the users who was supposed to have
Administrator rights but did not (i.e., The Administrator checkbox was
checked in the "Matrix-based security" form, but the user had no
Administrator capabilities).
I then re-added the user and added the user to the "Matrix-bas
Hello,
I am experiencing very odd access behavior on two different Jenkins
servers. Both servers are Win. 8.1 and both use Jenkins 1.580.1
Both servers use "Jenkins own User Database" and "Matrix based security".
I selected "Administrator" rights for 3 different users.
Now, only one of those t
