Troubleshooting
Problem
UID Chain is a mechanism which allows S-TAP (by way of K-Tap) to track the chain of users that occurred prior to a database connection. For example, a user may have changed users several times before connecting to the database; perhaps he ran "ssh informix@system1" then "su - db2inst1" then "su - " then "su - oracle9" before finally running "sqlplus scott/tiger@system2". With UID Chains, Guardium can trace this process back to the process that called it and so on back to the original (offending) user. You can configure UID Chain in your S-TAP configuration file using parameter HUNTER_TRACE. You can then add field Uid Chain (Session entity) to your reports to show the whole chain of users participating in the connection, back to the original user (informix in the example in this article). If there are several users in the chain before reaching the database connection, the value in the Uid Chain field in the report may be long and you may desire the report to show a string constant in the Uid Chain field instead, representing the specific chain of users. This article discuss the possbility of configuring a string constant to represent a specific chain of users in the Uid Chain field.
Resolving The Problem
Unfortunately, until the release of Guardium version 9.0, it is not possible to configure an Alias like a string constant value for a UID Chain value. An Enhancement Request (bugzilla 31693) has been opened requesting to add this capability to a future release or version.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21615992