New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jenkins PAM authentication issues in 12.1 #42

Closed
alonswartz opened this Issue Jul 4, 2013 · 5 comments

Comments

Projects
None yet
4 participants
@alonswartz
Member

alonswartz commented Jul 4, 2013

Reported by Dmytro Pishchukhin, workaround by Andy Korol on the forum

@jberends

This comment has been minimized.

Show comment
Hide comment
@jberends

jberends Aug 1, 2013

Want to confirm that this is the case after launching a jenkins 12.1 appliance. Provided administrator user and password fail to login and making the jenkins appliance not usable from the hub.

jberends commented Aug 1, 2013

Want to confirm that this is the case after launching a jenkins 12.1 appliance. Provided administrator user and password fail to login and making the jenkins appliance not usable from the hub.

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister Aug 5, 2013

Member

@jberends As I noted on the forum the workaround is confirmed working and as such this appliance is usable from the Hub (or anywhere else) once you have applied the workaround.

@alonswartz In case you didn't notice, John Palmer has posted on the forum, suggesting that the root of this problem is in fact permissions...

Member

JedMeister commented Aug 5, 2013

@jberends As I noted on the forum the workaround is confirmed working and as such this appliance is usable from the Hub (or anywhere else) once you have applied the workaround.

@alonswartz In case you didn't notice, John Palmer has posted on the forum, suggesting that the root of this problem is in fact permissions...

@alonswartz

This comment has been minimized.

Show comment
Hide comment
@alonswartz

alonswartz Aug 11, 2013

Member

Thanks @JedMeister. For completeness, the workaround as described by John Palmer:

chown jenkins:nogroup /var/lib/jenkins/plugins
/etc/init.d/jenkins restart
Member

alonswartz commented Aug 11, 2013

Thanks @JedMeister. For completeness, the workaround as described by John Palmer:

chown jenkins:nogroup /var/lib/jenkins/plugins
/etc/init.d/jenkins restart
@jberends

This comment has been minimized.

Show comment
Hide comment
@jberends

jberends Aug 12, 2013

I can confirm that this solution (correct the rights on the plugin dir) works.

Jochem Berends (JBits)
jberends@jbits.nl

On Aug 11, 2013, at 1:22 PM, Alon Swartz notifications@github.com wrote:

Thanks @JedMeister. For completeness, the workaround as described by John Palmer:

chown jenkins:nogroup /var/lib/jenkins/plugins
/etc/init.d/jenkins restart


Reply to this email directly or view it on GitHub.

jberends commented Aug 12, 2013

I can confirm that this solution (correct the rights on the plugin dir) works.

Jochem Berends (JBits)
jberends@jbits.nl

On Aug 11, 2013, at 1:22 PM, Alon Swartz notifications@github.com wrote:

Thanks @JedMeister. For completeness, the workaround as described by John Palmer:

chown jenkins:nogroup /var/lib/jenkins/plugins
/etc/init.d/jenkins restart


Reply to this email directly or view it on GitHub.

@Dude4Linux

This comment has been minimized.

Show comment
Hide comment
@Dude4Linux

Dude4Linux Aug 18, 2013

Member

I can also confirm that the workaround proposed by John Palmer worked for me.

Member

Dude4Linux commented Aug 18, 2013

I can also confirm that the workaround proposed by John Palmer worked for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment