OSA Requires JMS Passwords In Cleartext

(Doc ID 2298178.1)

Last updated on AUGUST 30, 2017

Applies to:

Oracle Stream Analytics - Version and later
Information in this document applies to any platform.


We are using JMS queues/topics in an OSA application. The configuration parameters that we specify for the applications are mentioned below:


Inside the OSA application, we reference this configuration in the context.xml as below:

<wlevs:adapter id="JMS-Out-EP" provider="jms-outbound">
<wlevs:instance-property name="jndiProviderUrl" value="${JMS.jndiProviderUrl}"/>
<wlevs:instance-property name="user" value="${JMS.user}"/>
<wlevs:instance-property name="password" value="${JMS.password}"/>
<wlevs:instance-property name="destinationJndiName" value="${JMS.destination}"/>
<wlevs:instance-property name="jndiFactory" value="${JMS.jndiFactory}"/>
<wlevs:instance-property name="eventType" value="AnyEvent"/>

As you can see above, the password for the jms is mentioned in cleartext. This is a high security risk. We need this password to be encrypted.

How to specify the jms password in encrypted form ?

What is the encryption length for the password?

What is the algorithm used in the encryption?



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms