We have figured out that this is due to Jenkins 2.139 updated libpam4j from
1.8 to 1.11, looks like 1.11 requires root to get authentication. If we
start Jenkins using root everything as far as logging in works, it breaks
all kinds of other things so we would rather not do this. Starting Jenkins
Our Jenkins server uses Active Directory for login management and the
Security Realm in Jenkins is set to: Unix user/group database. We are
currently running release 2.138.4 in Jenkins and everything works great. If
I update to any release above 2.138.4 all logins to Jenkins using a user in
AD
