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 a unique identifier. VIP EGW 9.11 transactions also include the RADIUS port number from the source validation server.
For example, the Request ID below indicates this transaction was from Enterprise Gateway version 9.11.0 running on a Windows (w) server at IP address 10.252.157.13, from a Validation Server on RADIUS port 1812. The second screenshot shows the source validation server on the VIP EGW.
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.
Other request ID prefixes:
VIPMGR: The transaction was performed by a VIP Administrator through the VIP Manager portal.
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 Portal flow:
myvip: The transaction was initiated by the VIP My VIP Portal flow:
Note: Logins specific to VIP SSP and My VIP can also be viewed by clicking View Audit Reports, then selecting Self-Service Portal or My VIP.