Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45841

Disable JNLP1/JNLP2/CLI1 by default on new installations

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • core, remoting
    • None

      It is almost one year since the release of JNLP4 protocol in Remoting 3.0. This protocol is available in Jenkins LTS since 2.32.1, and so far it demonstrates good stability being compared to JNLP2 and especially to JNLP3. The protocol was enabled by default in 2.46.x, and we do not have confirmed JNLP4 issues since that.

      I propose to disable the previous protocols

          [JENKINS-45841] Disable JNLP1/JNLP2/CLI1 by default on new installations

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Epic Link New: JENKINS-38833 [ 175240 ]
          Oleg Nenashev made changes -
          Remote Link New: This issue links to "Proposal in the ML (Web Link)" [ 17356 ]
          Oleg Nenashev made changes -
          Component/s New: remoting [ 15489 ]
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Oleg Nenashev made changes -
          Remote Link New: This issue links to "https://github.com/jenkinsci/remoting/pull/183 (Web Link)" [ 17375 ]
          Oleg Nenashev made changes -
          Remote Link New: This issue links to "https://github.com/jenkinsci/remoting/pull/182 (Web Link)" [ 17376 ]
          Oleg Nenashev made changes -
          Remote Link New: This issue links to "https://github.com/jenkinsci/jenkins/pull/2950 (Web Link)" [ 17377 ]
          Oleg Nenashev made changes -
          Link New: This issue is related to JENKINS-26580 [ JENKINS-26580 ]
          Oleg Nenashev made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

            oleg_nenashev Oleg Nenashev
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: