Enhancement: HTTP Request Action with Parameter Storage Credentials

bussdw · April 13, 2026, 3:06pm

This … doesn’t seem fully implemented? Building a workflow for an API that requires Basic Authorization has the workflow ask for which Basic Authorization parameter to use.

The problem? There doesn’t seem to be any way to create a Parameter for Basic Authorization. That simply doesn’t appear as an option:

While I would love to use OAuth 2.0 for this, the API simply doesn’t support it. I can certainly set the auth type to No Auth on the workflow and manually create the Authorization header in the action config, but it seems like we shouldn’t have to do that with this feature. Is this expected?

Takato · April 13, 2026, 6:32pm

Hi @bussdw , did you use the “Credential” option in the Parameter Storage page? (Category > Authentication, Type > Credential)

Topic		Replies	Views
HTTP Request Action Workflow ISC Discussion and Questions workflows , identity-security-cloud	15	4671	July 19, 2023
HTTP Action Trigger to disable Delta on a source ISC Discussion and Questions workflows , identity-security-cloud	2	375	July 19, 2023
There currently is no mechanism to secure data in an HTTP request. If you put sensitive information in the headers, like secrets and tokens, it will be output to the logs ISC Discussion and Questions workflows , apis , identity-security-cloud	7	610	July 19, 2023
Using Workflow's HTTP Request Action to Work With IdentityNow APIs ISC Community Knowledge Base workflows , apis	20	5374	February 24, 2026
Worflow HTTP Request Action ISC Discussion and Questions workflows , identity-security-cloud	2	57	March 2, 2026

Enhancement: HTTP Request Action with Parameter Storage Credentials

Related topics