Last updated on JUNE 28, 2017
Applies to:Oracle Tuxedo - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Consider a Tuxedo application connecting to Oracle Database using XA interface.
TUXEDO will act as transaction manager deciding when XA functions must be executed, in particular xa_open() to connect to Oracle database instance.
OPENINFO string is used by Tuxedo to define what string must be passed to xaoopen() function. But the content of its string does NOT depend on Tuxedo but depends on Oracle database.
For a complete description of data passed in OPENINFO string, please refer to Oracle Database Advanced Application Developer's Guide :
This chapter explains how to use the Oracle XA library. Typically, you use this library in applications that work with transaction monitors. The XA features are most useful in applications in which transactions interact with multiple databases."
The user credentials are defined within OPENINFO string in Tuxedo ubb configuration file. On Tuxedo side, the user password passed into OPENINFO string is encrypted. When activating Oracle XA traces within OPENINFO string, the password is displayed in plain text.
Why is the user password written in plain text in Oracle XA trace log file ?
From a security standpoint, is there a way to prohibit the logging of the user credentials in the Oracle Database XA logs?
The password of the user connected to Oracle through xa_open() is in plain text in XA Oracle log file even if it has been encrypted in Tuxedo configuration file :
Excerpt from Oracle XA trace log file xa_NULL01182012.trc file stored in /home/test/oxa/log file :
Excerpt from the matching Tuxedo ubb configuration file :
The "@@A097E47722D4@@ "substring within OPENINFO string proves the user password encryption works well on Tuxedo side. No password in plain text is passed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms