[JIRA] (JENKINS-47281) swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects

7 views
Skip to first unread message

o.v.nenashev@gmail.com (JIRA)

unread,
Feb 26, 2018, 3:28:29 AM2/26/18
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Unassigned
 

KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

Jenkins / Improvement JENKINS-47281
swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects
Change By: Oleg Nenashev
Assignee: Kohsuke Kawaguchi
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

me@basilcrow.com (JIRA)

unread,
Jun 1, 2019, 2:05:06 PM6/1/19
to jenkinsc...@googlegroups.com
Basil Crow updated an issue
 
Jenkins / New Feature JENKINS-47281
Change By: Basil Crow
Issue Type: Improvement New Feature
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

me@basilcrow.com (JIRA)

unread,
Jun 1, 2019, 2:13:02 PM6/1/19
to jenkinsc...@googlegroups.com

me@basilcrow.com (JIRA)

unread,
Jun 1, 2019, 2:41:02 PM6/1/19
to jenkinsc...@googlegroups.com
Basil Crow closed an issue as Duplicate
 

This looks like a duplicate of JENKINS-25421. The workaround is to enable CSRF on the Jenkins master.

Change By: Basil Crow
Status: Open Closed
Resolution: Duplicate

me@basilcrow.com (JIRA)

unread,
Jun 2, 2019, 10:04:03 AM6/2/19
to jenkinsc...@googlegroups.com
Basil Crow commented on Bug JENKINS-47281
 
Re: swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects

Is this still a bug on recent versions of Jenkins core and Swarm client? I just tried connecting to a Jenkins master (2.150.1) with Swarm client both with and without CSRF enabled on the Jenkins master, and things worked just fine.

me@basilcrow.com (JIRA)

unread,
Jun 2, 2019, 10:04:06 AM6/2/19
to jenkinsc...@googlegroups.com
Basil Crow edited a comment on Bug JENKINS-47281
Is this still a bug on recent versions of Jenkins core and Swarm client? I just tried connecting to a Jenkins master (2.150.1) with Swarm client 3.16 both with and without CSRF enabled on the Jenkins master, and things worked just fine.
Reply all
Reply to author
Forward
0 new messages