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

Support secret text credentials in the http request plugin

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • http-request-plugin
    • None
    • Jenkins 2.389
      HTTP Request Plugin Version 1.16

      Authenticate with secret-text credentials as follows

      def response = httpRequest(url: apiUrl, authentication: 'benipeled-test-httpRequest-secret-key', consoleLogResponseBody: true)

      Fail with the following non-exists msg

      16:12:39  java.lang.IllegalStateException: Authentication 'benipeled-test-httpRequest-secret-key' doesn't exist anymore
      16:12:39      at jenkins.plugins.http_request.HttpRequestExecution.<init>(HttpRequestExecution.java:239)
      16:12:39      at jenkins.plugins.http_request.HttpRequestExecution.from(HttpRequestExecution.java:163)
      16:12:39      at jenkins.plugins.http_request.HttpRequestStep$Execution.run(HttpRequestStep.java:394)
      16:12:39      at jenkins.plugins.http_request.HttpRequestStep$Execution.run(HttpRequestStep.java:383)
      16:12:39      at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
      16:12:39      at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
      16:12:39      at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
      16:12:39      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
      16:12:39      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
      16:12:39      at java.base/java.lang.Thread.run(Thread.java:829)
      16:12:39  Finished: FAILURE 

      I see it comes from [0] but I'm not sure why auth == null in this case

      [0] https://github.com/jenkinsci/http-request-plugin/blob/master/src/main/java/jenkins/plugins/http_request/HttpRequestExecution.java#L223-L253

          [JENKINS-70718] Support secret text credentials in the http request plugin

          Mark Waite added a comment -

          The message may be poorly phrased for this context. I suspect it should say something like "The secret text credential type is not supported by the http request plugin, use the username / password credential type".

          Could you create a username / password credential type and try the same operation?

          Mark Waite added a comment - The message may be poorly phrased for this context. I suspect it should say something like "The secret text credential type is not supported by the http request plugin, use the username / password credential type". Could you create a username / password credential type and try the same operation?

          Beni Peled added a comment -

           
          markewaite yes, u/p type works as expected, 
          If so it's not a bug but an RFE to support secret-text type
           

          Beni Peled added a comment -   markewaite yes, u/p type works as expected,  If so it's not a bug but an RFE to support secret-text type  

          Charles added a comment -

          How would you expect a secret-text type to work?  Would the authorization header be a "Basic" scheme?  If so, would the secret be the password portion?  If so, what would the value username portion be?

          Charles added a comment - How would you expect a secret-text type to work?  Would the authorization header be a "Basic" scheme?  If so, would the secret be the password portion?  If so, what would the value username portion be?

            janario Janario Oliveira
            benipeled Beni Peled
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: