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

Can't authenticate with HTTPS client cert + username/password

XMLWordPrintable

      My subversion repository requires both a https client cert as well as subversion username/password.

      Unfortunately, the jenkins subversion authentication config presents a radio button to select one of: username/password, SSH public key, HTTPS client cert.

      I have tried to work around this by modifying the .subverion/servers file to specify the name of my pkcs#12 file and the password/passphrase for it, and then select the username/password radio button. But unfortunately, I can't seem to get it to work.

          [JENKINS-14792] Can't authenticate with HTTPS client cert + username/password

          Frédéric Camblor added a comment -

          Plugin is not using the .svn/ configuration directory. More infos provided here

          Frédéric Camblor added a comment - Plugin is not using the .svn/ configuration directory. More infos provided here

          Oleg Nenashev added a comment -

          No response from the requester (2-year timeout)

          Oleg Nenashev added a comment - No response from the requester (2-year timeout)

          Oleg Nenashev added a comment -

          Reopened the issue according to comments from danielbeck

          Oleg Nenashev added a comment - Reopened the issue according to comments from danielbeck

          Oleg Nenashev added a comment -

          A new CredentialsProvider (as well as internal logic) is required for such feature

          Oleg Nenashev added a comment - A new CredentialsProvider (as well as internal logic) is required for such feature

          Mark Waite added a comment -

          The scm sync configuration plugin is deprecated. No further work is expected on the plugin.

          Users of this plugin are encouraged to migrate their jobs to Pipeline Plugin, so that their jobs will be specified in pipeline code that can be checked into an SCM, all without using the SCM Sync configuration plugin.

          Users of this plugin are also encouraged to use the Configuration as Code Plugin to specify the configuration of their Jenkins server in a file which can be checked into an SCM, all without using the SCM Sync configuration plugin.

          Mark Waite added a comment - The scm sync configuration plugin is deprecated. No further work is expected on the plugin. Users of this plugin are encouraged to migrate their jobs to Pipeline Plugin, so that their jobs will be specified in pipeline code that can be checked into an SCM, all without using the SCM Sync configuration plugin. Users of this plugin are also encouraged to use the Configuration as Code Plugin to specify the configuration of their Jenkins server in a file which can be checked into an SCM, all without using the SCM Sync configuration plugin.

            fcamblor Frédéric Camblor
            dallasclement Dallas Clement
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: