[JIRA] [github-oauth-plugin] (JENKINS-14524) Slave agent authorization 401
Title: Message Title fayyaz rehman commented on JENKINS-14524 Re: Slave agent authorization 401 i am having the same issue Failing to obtain https://ci.corvit.lab/jenkins/computer/slave3/slave-agent.jnlp java.io.IOException: Failed to load https://ci.corvit.lab/jenkins/computer/slave3/slave-agent.jnlp: 401 Unauthorized at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:275) at hudson.remoting.Launcher.run(Launcher.java:219) at hudson.remoting.Launcher.main(Launcher.java:192) Waiting 10 seconds before retry Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-14524) Slave agent authorization 401
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-14524 Slave agent authorization 401 Change By: Sam Gleske Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-14524) Slave agent authorization 401
Title: Message Title Sam Gleske commented on JENKINS-14524 Re: Slave agent authorization 401 Since the latest LTS release of Jenkins is 1.609.1 and it was reported to work okay in 1.590 I'm closing this as resolved. If you feel it is not resolved then feel free to re-open the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-14524) Slave agent authorization 401
Jakub Czaplicki commented on JENKINS-14524 Slave agent authorization 401 The issue also occurs when Active Directory is used as access control (jenkins ver. 1.554). For jenkins ver. 1.590 works OK. So somewhere between 1.554 and 1.590 the issue has been fixed for Active Dir. 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/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-14524) Slave agent authorization 401
Daniel Beck commented on JENKINS-14524 Slave agent authorization 401 Newer versions of Jenkins also use a secret URL parameter for authorization by default. Check the slave's index page to see the value. 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/d/optout.
