If I look more closely at the ra.xml
- the following section handles the password credentials
<authentication-mechanism>
<authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
<credential-interface>javax.resource.spi.security.PasswordCredential</credential-interface>
</authentication-mechanism>
As per the connection_1_6.xsd (used by ra.xml)
The credential-interfaceType specifies the interface that the
resource adapter implementation
supports for the representation of the credentials. This element(s)
that use this type,
i.e. credential-interface, should be used by application server to
find out the Credential
interface it should use as part of the security contract.
The possible values are:
javax.resource.spi.security.PasswordCredential
org.ietf.jgss.GSSCredential
javax.resource.spi.security.GenericCredential
So I can use only the above 3 interfaces - and none of them actually takes
in a encrypted password along with an algorithm - so that it can be
decrypted.
Does this mean - since my MDB (message driven beans) use ra.xml to connect
to the messageBroker - I have to write my own implementation to connect to
JMS Broker (that takes in algorithm name and encrypted password?)
regards
D
--
View this message in context:
http://activemq.2283324.n4.nabble.com/How-to-encrypt-password-in-broker-config-xml-and-ra-xml-tp4681449p4681476.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
