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

[jenkins-infra-bot]

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.(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

---

Originally reported by benipeled, imported from: Support secret text credentials in the http request plugin

• assignee: janario
• status: Open
• priority: Minor
• component(s): http-request-plugin
• resolution: Unresolved
• votes: 1
• watchers: 5
• imported: 20260702-081740

Raw content of original issue

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

environment

Jenkins 2.389<br/>
HTTP Request Plugin Version 1.16

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original 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?
  

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?

[jenkins-infra-bot]

benipeled:

• Original comment link
• Raw content of original comment:

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

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

[jenkins-infra-bot]

chas:

• Original comment link
• Raw content of original 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?
  

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?

[jenkins-infra-bot]

dshvedchenko:

• Original comment link
• Raw content of original comment:

  Secret text should go just to to header: Authorization: <secret text>.
  
  workaround for secrets,. just using CustomHeader part of this plugin and create Authorization header. and pass secret via env variable etc
  

Secret text should go just to to header: Authorization: .

workaround for secrets,. just using CustomHeader part of this plugin and create Authorization header. and pass secret via env variable etc