Java Naming and Directory Interface (JNDI) credential is displayed in cleartext on JBoss server.log in RSA Identity Management and Governance
Originally Published: 2016-12-12
Article Number
Applies To
RSA Version/Condition: 6.9.1
Platform: JBoss
Issue
2016-11-22 00:06:32,403 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:
{java.naming.security.principal=aveksaUser, java.naming.security.credentials=Aveksa123}
Resolution
To change the specific org.hibernate category from INFO to ERROR level logging to hide the logging
- Navigate to Admin > System and click on the Logs tab.
- Click the Settings button and the System Log Settings popup will be displayed.
- On the popup, click the Advanced button on the Category Log Levels section.
- In the Category Log Levels section, do the following:
- Select org.hibernate from the Group drop-down list
- Select org.hibernate.util.NamingHelper from the Category drop-down list (it is almost at the bottom of the list).
- Click the Add button to display org.hibernate.util.NamingHelper and the corresponding log level.
- Select ERROR for org.hibernate.util.NamingHelper.
- Click OK button at the bottom of the page
- Restart ACM and then verify that the below INFO line (org.hibernate.util.NamingHelper) is now suppressed:
2016-11-29 18:35:39,321 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:
{java.naming.security.principal=aveksaUser, java.naming.security.credentials=Aveksa123}
To change the password on the fly in hibernate.cfg.xml
- Login to your system as root.
- Edit the hibernate.cfg.xml by changing the value of the JNDI property name hibernate.jndi.java.naming.security.credentials from Aveksa123 to your desired password. To do this, type the following command to edit the file:
acm-691:~ # vi /home/oracle/jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/ WEB-INF/hibernate.cfg.xml
- Once in the file, make the change to a new value, shown here as the text SomethingElse:
<?xml version='1.0' encoding='utf-8'?> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN" "http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd"> <hibernate-configuration> <session-factory> <!-- Database connection settings --> <property name="connection.datasource">java:comp/env/jdbc/avdb</property> <property name="transaction.factory_class">org.hibernate.transaction.JDBCTransactionFactory</property> <property name="hibernate.jndi.java.naming.security.principal">aveksaUser</property> <property name="hibernate.jndi.java.naming.security.credentials">SomethingElse</property>
- Save the changes by pressing Esc then :wq.
- Restart ACM.
acm start
Related Articles
How business source filtering works in an account access and ownership review in RSA Identity Governance & Lifecycle 46Number of Views Cloud Administration Enable SecurID DS100 OTP Credential API 66Number of Views RSA MFA Agent for Windows delay getting the MFA prompt after credentials are entered 100Number of Views In the General Settings associations page clicking reset creates System Internal Error 47Number of Views Advisory for Migrating credentials from RSA SecurID Software Token 4.2.3 to SecurID Authenticator 5.1 for macOS 218Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager Upgrade Process
Don't see what you're looking for?