How to set Authorization Header for InvokeRESTAPI activity?
Article ID: KB0071479
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessWorks Container Edition | 2.8.x |
Description
Currently, we can define the Authorization header from the HTTP Client resource using an Identity provider.
Another alternative is using a Dynamic Header in the Invoke REST API activity and defining the authorization there.
What happens if you have defined the Authorization header from the HTTP Client resource and the Dynamic Header of the activity?
Another alternative is using a Dynamic Header in the Invoke REST API activity and defining the authorization there.
What happens if you have defined the Authorization header from the HTTP Client resource and the Dynamic Header of the activity?
Issue/Introduction
Options for setting authorization header for InvokeRESTAPI activity
Resolution
The expected behavior is that the Dynamic Header value for the Authorization header will overwrite the value injected by the Identity provider in the HTTP Client resource.
You can refer to the attached example project.
You can refer to the attached example project.
Additional Information
https://docs.tibco.com/pub/bwce/2.8.1/doc/html/binding-palette/http-client.htm
https://docs.tibco.com/pub/bwce/2.8.1/doc/html/binding-palette/identity-provider.htm
https://docs.tibco.com/pub/bwce/2.8.1/doc/html/binding-palette/invoke-rest-api.htm
https://docs.tibco.com/pub/bwce/2.8.1/doc/html/binding-palette/identity-provider.htm
https://docs.tibco.com/pub/bwce/2.8.1/doc/html/binding-palette/invoke-rest-api.htm
Attachments
Feedback
Yes
No
Powered by
