|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Still scowering the net for a solutiojn..not much out there. Found this old, failry definiative blog post from 2009..
############################################
Jon Schewe wrote:
> Yes, this is the case if you have shadow passwords, which most people
> do. You can either run hudson as root or give access to /etc/shadow to a
> group, perhaps called 'shadow', and then add the hudson user to that
> group. Then it'll work.
>
> Kohsuke Kawaguchi wrote:
>> I've heard from some users that PAM auth can only authenticate the user
>> that Hudson is running as, unless Hudson is run as root.
>>
##########################################
So if I change jenkins to run as root, authentication does indeed work (although I see other breakages launching slaves due which I would now have to sort out)
Considering that I have been running for 6 months as jenkins without any problems, I having a hard time buying that running as root is a hard requirement PAM auth. At least it has not been true for us for about 6 months. There's got to be something else going on.