How to use the Request ID to determine the VIP Enterprise Gateway version and IP address of all VIP Enterprise Gateways sending requests to the VIP Cloud. This data can help administrators reconcile all active servers within their organization. The request ID is also a clue as to the source of other VIP transactions.
A Request ID is included with every end-user transaction sent to the VIP Cloud by the VIP Enterprise Gateway and can be seen in the VIP Manager end-user transaction reports. The request ID consists of the VIP Enterprise Gateway version, platform, local IP address, and unique identifier. In the request ID below, 9_9_2 is the version, w = Windows (l is Linux), 10_255_1_141 is the local IP address, and 1146892231 is a unique transaction identifier.
An exported .csv file from a VIP Manager end-user transaction report will include each request ID and can be used to determine active VIP Enterprise Gateway instances for that time frame. If applicable, run the same report from any other VIP tenants (JHash).
Other request ID prefixes:
VIPMGR: The transaction was performed by a VIP Administrator through the VIP Manager portal. (The View Audit Reports link shows the admin ID that performed the action)
ADFS: Consists of the ADFS plugin version, local IP address, and unique identifier. In the request ID below, 9_9_0 is the version, 10_253_38_172 is the local ADFS server IP address, and 36466 is a unique transaction identifier.
VIPLOGIN: The transaction was initiated through the VIP Login (SAML), Azure, OIDC, or the MyVIP portal flow (including Azure OIDC).
VIP_SSP: The transaction was initiated by the VIP Self-Service IdP flow:
Note: Logins specific to VIP SSP and My VIP can be viewed by clicking View Audit Reports, then selecting Self-Service Portal or My VIP.