Sample for RenameHeader connector in Tibco Mashery
Article ID: KB0073549
Updated On:
| Products | Versions |
|---|---|
| TIBCO Cloud API Management | ALL |
Description
A possible usecase for this connector is:
- When Mashery is enforcing a authentication and reads the Authorization header
- But the Backend requires:
-- a different Authorization header(for e.g Basic Auth)
-- as well as the original token from the client/user
- When Mashery is enforcing a authentication and reads the Authorization header
- But the Backend requires:
-- a different Authorization header(for e.g Basic Auth)
-- as well as the original token from the client/user
Issue/Introduction
This article provides sample usage for RenameHeader connector in Tibco Mashery
Environment
All Supported Platforms
Resolution
Using the RenameHeader connector, Mashery can send:
- the new Authorization header as expected by the backend
- and the original Authz token, via a new header created by the connector.
Please refer to the attached Mashery_headerRename.pdf for sample config entries.
- the new Authorization header as expected by the backend
- and the original Authz token, via a new header created by the connector.
Please refer to the attached Mashery_headerRename.pdf for sample config entries.
Attachments
Feedback
Yes
No
Powered by
