Achim, do you have any pointer for me where this is implemented? I couldn't figure it out. Another PCI requirement for us is to use an encrypted connection to our database. Oracle supports this by setting additional connection properties [1]. This is (also) not supported yet. You are interested in this patch?
[1] http://docs.oracle.com/cd/B28359_01/network.111/b28530/asojbdc.htm Best, Christian On Mon, Nov 19, 2012 at 3:57 PM, Achim Nierbeck <bcanh...@googlemail.com>wrote: > Hi Christian, > > to my knowledge Karaf supports both, though for jasypt you probably need > to use a 3.0.0-SNAPSHOT right now. > Need to check if 2.3.x also supports jasypt. > > regards, Achim > > > 2012/11/19 Christian Müller <christian.muel...@gmail.com> > >> Hello! >> >> We use the database locking mechanism in Karaf (2.2.2) to support >> Failover. We have to use the database locking machanism because we do not >> have a shared file system in place. We are also forced by PCI [1] to not >> use passwords in plain text. As I can see from the source code [2], Karaf >> doesn't support this right now (e.g. via Jasypt or so). >> >> I would like to open a JIRA for it, if I didn't overlooked something and >> Karaf already support this requirement. At present, we hve to work around >> this by subclassing the DefaultJDBCLock and extend it for our own needs. >> >> [1] >> http://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard >> [2] >> https://svn.apache.org/repos/asf/karaf/trunk/main/src/main/java/org/apache/karaf/main/lock/DefaultJDBCLock.java >> >> Thanks in advance, >> Christian >> > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> > Commiter & Project Lead > blog <http://notizblog.nierbeck.de/> > --
