X-CLIENT-TRANSACTION-ID is not propagated to the success callback URL - Symantec Identity Security Platform (IDSP)

Products

• Symantec Identity Security Platform - IDSP (formerly VIP Authentication Hub)

Issue/Introduction

You observe that the X-CLIENT-TRANSACTION-ID header, used for end-to-end log correlation, is missing from the final success callback URL during an OIDC Authorization Code Flow.

While the identifier is present in the initial authentication steps and appears in the HTTP 302 redirect response headers, it is not appended as a query parameter to the final redirect location sent to the browser. This prevents your backend systems (such as Apigee) from correlating the client-side transaction with the server-side logs during the successful completion of the flow.

Environment

• Product: Symantec Identity Security Platform (IDSP) / VIP Authentication Hub
• Version: 4.0.2
• Flow: OIDC Authorization Code Flow

Cause

This behavior is confirmed as a product limitation. While the IDSP server maintains the transaction ID throughout the authentication lifecycle, the logic responsible for building the final success redirect URL does not include the client-supplied transaction ID.

Resolution

This issue is confirmed and is targeted to be fixed in release 4.1.1.

As this release target is tentative, please raise a Support ticket to check for any specific exceptions or updates to the delivery schedule.