Adding PAM as a user realm #809
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@TheKangaroo It looks like there are at least syntax problems with the groovy. @rtyler I sort of feel like |
|
Hi. Thanks for raising this PR, but I'm going to close it due to inactivity. Please reopen it if you're still interested in getting this merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Like #606 for LDAP, this PR adds the pam authentication for Jenkins.
The configuration of pam Auth works fine for me.
I still have trouble with Jenkins only supporting one security realm provider (https://issues.jenkins-ci.org/browse/JENKINS-15063).
Therefore as soon as I configure PAM auth with puppet, the puppet Jenkins configuration user (who is in Jenkins own user database) stops working and there seems to be no way, to automate the deployment of Jenkins with pam.
The only workaround I can think of would be a user in the Linux system with the exact same username and password as the Jenkins admin+initialAdminPassword.
But I'm not sure how to implement this right now.
Any ideas or suggestions on that?