Hi Vinu, just re-read your mail. If you are not using pax-jdbc but plain blueprint with configAdmin then check following guide [1] for how to configure encryption of properties. Should work with "cm" instead of "etc" managed properties as well.
[1] https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.0/html/Security_Guide/files/ESBSecurityEncryptProperties.html Cheers, Michael 2015-03-24 14:17 GMT+01:00 Michael Täschner <[email protected]>: > Hi Vinu, > > I raised this issue a couple of weeks ago and it is being looked at right > now. Please check https://ops4j1.jira.com/browse/PAXJDBC-65 > > Cheers, > Michael > > 2015-03-24 12:43 GMT+01:00 <[email protected]>: > >> Facing an issue with connecting to an MS SQL server database using >> Jasypt encrypted passwords. Same code is working fine with a postgresql >> database with same userid/password. Database credentials are in a >> properties file loaded using configAdmin with blueprint. Properties file is >> as below >> >> >> >> db1.driver=org.postgresql.Driver >> >> db1.url=jdbc:postgresql://localhost:5432/db1 >> >> db1.user=user >> >> db1.password=ENC(lkjalsdkalsdlksd;alk) >> >> >> >> db2.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver >> >> db2.url=jdbc:sqlserver://localhost:1433;databaseName=db2 >> >> db2.user=user >> >> db2.password=ENC(lkjalsdkalsdlksd;alk) >> >> >> >> If I remove the ENC enclosure and provide the plain text password for SQL >> Server database, everything is fine. Any issue reported specific to MS SQL >> Server ? >> >> >> >> -Vinu >> The information contained in this electronic message and any attachments >> to this message are intended for the exclusive use of the addressee(s) and >> may contain proprietary, confidential or privileged information. If you are >> not the intended recipient, you should not disseminate, distribute or copy >> this e-mail. Please notify the sender immediately and destroy all copies of >> this message and any attachments. WARNING: Computer viruses can be >> transmitted via email. The recipient should check this email and any >> attachments for the presence of viruses. The company accepts no liability >> for any damage caused by any virus transmitted by this email. >> www.wipro.com >> > >
