Quantcast
Jenkins › Jenkins issues

[JIRA] (JENKINS-11663) Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled

classic Classic list List threaded Threaded
♦
♦
 5 messages Options
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-11663) Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled

JIRA noreply@jenkins-ci.org
Nicholas Hall created JENKINS-11663:
---------------------------------------

             Summary: Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled
                 Key: JENKINS-11663
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11663
             Project: Jenkins
          Issue Type: Bug
          Components: swarm
            Reporter: Nicholas Hall
            Assignee: Kohsuke Kawaguchi
            Priority: Trivial
         Attachments: Client.java.diff

We have enabled LDAP authentication for Jenkins, but do not have authorization enabled ('Anyone can do anything').

We do not pass a username or password for the swarm clients.  This results in a 401 during the jnlp connection phase.

I've attached a very simple code change to hudson.plugins.swarm.Client.java that works in our environment.  Under the condition that a username and password aren't available, do not add the '-credential' switch to the Main args.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-11663) Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled

JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

sogabe reassigned JENKINS-11663:
--------------------------------

    Assignee: sogabe  (was: Kohsuke Kawaguchi)
   

> Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-11663
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11663
>             Project: Jenkins
>          Issue Type: Bug
>          Components: swarm
>            Reporter: Nicholas Hall
>            Assignee: sogabe
>            Priority: Trivial
>         Attachments: Client.java.diff
>
>
> We have enabled LDAP authentication for Jenkins, but do not have authorization enabled ('Anyone can do anything').
> We do not pass a username or password for the swarm clients.  This results in a 401 during the jnlp connection phase.
> I've attached a very simple code change to hudson.plugins.swarm.Client.java that works in our environment.  Under the condition that a username and password aren't available, do not add the '-credential' switch to the Main args.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-11663) Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160375#comment-160375 ]

SCM/JIRA link daemon commented on JENKINS-11663:
------------------------------------------------

Code changed in jenkins
User: Seiji Sogabe
Path:
 client/src/main/java/hudson/plugins/swarm/Client.java
http://jenkins-ci.org/commit/swarm-plugin/992f49199868f0e9d8698aa48a93428b177eb018
Log:
  [JENKINS-11663] Swarm Client fails to connect to Jenkins when Authentication is enabled but
Authorization is diabled


Compare: https://github.com/jenkinsci/swarm-plugin/compare/54bf000...992f491


               

> Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-11663
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11663
>             Project: Jenkins
>          Issue Type: Bug
>          Components: swarm
>            Reporter: Nicholas Hall
>            Assignee: sogabe
>            Priority: Trivial
>         Attachments: Client.java.diff
>
>
> We have enabled LDAP authentication for Jenkins, but do not have authorization enabled ('Anyone can do anything').
> We do not pass a username or password for the swarm clients.  This results in a 401 during the jnlp connection phase.
> I've attached a very simple code change to hudson.plugins.swarm.Client.java that works in our environment.  Under the condition that a username and password aren't available, do not add the '-credential' switch to the Main args.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-11663) Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160376#comment-160376 ]

dogfood commented on JENKINS-11663:
-----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_swarm #33|http://ci.jenkins-ci.org/job/plugins_swarm/33/]
     [JENKINS-11663] Swarm Client fails to connect to Jenkins when Authentication is enabled but (Revision 992f49199868f0e9d8698aa48a93428b177eb018)

     Result = SUCCESS
Seiji Sogabe :
Files :
* client/src/main/java/hudson/plugins/swarm/Client.java

               

> Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-11663
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11663
>             Project: Jenkins
>          Issue Type: Bug
>          Components: swarm
>            Reporter: Nicholas Hall
>            Assignee: sogabe
>            Priority: Trivial
>         Attachments: Client.java.diff
>
>
> We have enabled LDAP authentication for Jenkins, but do not have authorization enabled ('Anyone can do anything').
> We do not pass a username or password for the swarm clients.  This results in a 401 during the jnlp connection phase.
> I've attached a very simple code change to hudson.plugins.swarm.Client.java that works in our environment.  Under the condition that a username and password aren't available, do not add the '-credential' switch to the Main args.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-11663) Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

sogabe resolved JENKINS-11663.
------------------------------

    Resolution: Fixed
   

> Swarm Client fails to connect to Jenkins when Authentication is enabled but Authorization is diabled
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-11663
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11663
>             Project: Jenkins
>          Issue Type: Bug
>          Components: swarm
>            Reporter: Nicholas Hall
>            Assignee: sogabe
>            Priority: Trivial
>         Attachments: Client.java.diff
>
>
> We have enabled LDAP authentication for Jenkins, but do not have authorization enabled ('Anyone can do anything').
> We do not pass a username or password for the swarm clients.  This results in a 401 during the jnlp connection phase.
> I've attached a very simple code change to hudson.plugins.swarm.Client.java that works in our environment.  Under the condition that a username and password aren't available, do not add the '-credential' switch to the Main args.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Loading...
Powered by Nabble Edit this page