This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Using WAS 5.1. The Connection Pooling works just great however I cannot continue to allow my DB ID/Password to be visible to the users of the WAS console (currently it is in the Custom Properties tab of the Connection Pool. What do I need to do in order to eliminate this - Ideally I'd like to place the DB ID/PW into an encrypted file and decrypt it when the pool is created? Any Help??
Open the server configuration file and select the security tab. Under the section "Jaas Authentication Entries" click the add button. Fill in the data for the alias (can be anything but I use DefaultNode/UserId), user id, and the password (note the description is optional). You can also do the previous part in the admin console somewhere but I can't remember where off the top of my head.
Go to the administrator console, expand the Resources node and select jdbc providers. Click the link to your data source from the appropriate scope. Select data sources from additional properties (at bottom) and then select your data source from the list.
Scroll down and change container-managed (or component-managed if necessary) authentication alias to DefaultNode/UserId (or whatever you specified the alias to be). Finally click Ok then save.
Your userid and password will be stored somewhere under the servers directory in security.xml. If you open it up you'll notice that the password has been encrypted.