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

Support -cert and -noCertificateCheck with -webSocket

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • remoting
    • None

      The only way to make the agent connect to a Jenkins master with a self-signed HTTPS certificate seems to be by adding the certificate in the host. This is a problem with the Docker image because of the need to extend it.

      The options -cert and -noCertificateCheck is already present in the remoting library, but not available for use with the -webSocket.

          [JENKINS-64760] Support -cert and -noCertificateCheck with -webSocket

          Felipe Santos created issue -
          Felipe Santos made changes -
          Link New: This issue is related to JENKINS-64758 [ JENKINS-64758 ]
          Felipe Santos made changes -
          Remote Link New: This issue links to "docker-inbound-agent#17 (Web Link)" [ 26478 ]
          Felipe Santos made changes -
          Remote Link New: This issue links to "docker-inbound-agent#38 (Web Link)" [ 26479 ]
          Felipe Santos made changes -
          Remote Link New: This issue links to "kubernetes-plugin PR #941 (Web Link)" [ 26480 ]
          Mark Waite made changes -
          Assignee Original: Jeff Thompson [ jthompson ]

            Unassigned Unassigned
            felipecassiors Felipe Santos
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: