+

Search Tips   |   Advanced Search

JMS Password Store

We can use the JMS Password Store to store the intercepted user passwords in a JMS queue from where the JMS clients read the passwords. The JMS Password Store was formerly known as the WebSphere® MQ Everyplace® Password Store.

The JMS Password Store provides the necessary function to store the intercepted user passwords in a JMS provider Queue from where any JMS client can read them. For example, the SDI.

The JMS Password Store package consists of the Storage Component and the JMS Password Store Connector. For more information about the JMS Password Store Connector, see SDI v7.2 Reference Guide. The storage component is actually the Password Store, which is started by the Password Synchronizer. The JMS Password Store Connector is a specialized connector on the SDI side that can retrieve passwords that are stored by the configured JMS Provider.

The class for this password store is: com.ibm.di.plugin.pwstore.jms.JMSPasswordStore


Apache ActiveMQ driver

To use ActiveMQ as the JMS provider for the JMS Password Store component, set the jmsDriverClass property in pwsync.props to com.ibm.di.plugin.pwstore.jms.driver.ActiveMQ. The ActiveMQ driver has the following parameter.

jms.broker - the ActiveMQ server address such as protocol, IP address, and TCP port number. For example, tcp://activeMQhost:61616 or ssl://activeMQhost:61617 to use SSL connection.


IBM WebSphere MQ Everyplace driver

The IBM WebSphere MQ Everyplace driver is responsible to create the IBM WebSphere MQ Everyplace Queue Manager and to retrieve the required connection objects. To use IBM WebSphere MQ Everyplace as the JMS provider for the JMS Password Store component, the jmsDriverClass property in the pwsync.props file must be set to com.ibm.di.plugin.pwstore.jms.driver.IBMMQe. Note: You must create an IBM WebSphere MQ Everyplace Queue Manager. To create it, use the IBM WebSphere MQ Everyplace Configuration utility, which is bundled with the Password Synchronizer. For more information about the IBM WebSphere MQ Everyplace Configuration utility, see MQe Queue Manager setup.


IBM WebSphere MQ driver

The IBM WebSphere MQ driver is responsible to establish the connection with the IBM WebSphere MQ JMS provider. To use IBM WebSphere MQ as the JMS provider for the JMS Password Store component, set the jmsDriverClass property in the pwsync.props to: com.ibm.di.plugin.pwstore.jms.driver.IBMMQ The IBM WebSphere MQ driver has the following parameters:

If you use SSL with the IBM WebSphere MQ driver, use the properties in the SSL Java Properties table inCommon configuration and utilities of password synchronization plug-ins to establish a relationship between JMS Password Store and IBM WebSphere MQ.

See the IBM WebSphere MQ Server documentation for configuration information.


Microbroker driver

For users with existing Microbroker installations, a Microbroker driver is provided. This driver is responsible to establish a connection with the Microbroker provider. To use Microbroker as the JMS provider for the JMS Password Store component, set the jmsDriverClass property in the pwsync.props file to: com.ibm.di.plugin.pwstore.jms.driver.IBMMB. The Microbroker driver has the following parameters:

Note: To use Microbroker as the JMS Password Store, a few Microbroker JAR files are needed. For a sample list of the required JAR files, see the "JMS Connector" section in SDI v7.2 Reference Guide.


JMS script driver

The user-defined JMS script drivers are not supported by the JMS Password Store. The JavaScript engine is not bundled with the Password Synchronizer.