Set the Partner Identity for Request
Using transformation file to set partner identify for request.
TIBCO API Exchange Gateway supports multiple identity types for identification of the requester. These identities use different protocol standards to support either transport level identification or request-based identification. In addition to the standards-based protocols, TIBCO API Exchange Gateway also provides a way to derive custom identities from either the payload message of the request or the transport context of the request.
The XSLT transformation file in the parse step can be used to populate the partner identity for the request. If the partner identity is set by the parse XSLT file, it overrides any other standards-based identity associated with the request.
When a standards-based identity is associated with the request which gets overridden by the parse XSLT, the original partner identity is stored as a row in the ASG_TRANSACTION_KEYS table that is associated with the audit trail log record of the request in the ASG_TRANSACTIONS table. The override log records or such credential mapping records are stored with a value of incomingPartner for the key_type column.