Different ways to pass a ssl_password for the connection factory being looked up from a JNDI server.

Different ways to pass a ssl_password for the connection factory being looked up from a JNDI server.

book

Article ID: KB0087501

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Message Service -
Not Applicable -

Description

Resolution:
Description:
===========
Because connection factories do not contain the ssl_password (for security reasons),  what are the possible ways to pass a ssl_password for the connection factory being looked up from JNDI server?

Resolution:
=========

There are several ways to set the ssl_password for the connection factory being looked up from JNDI server:

1). The EMS client API wiill attempt to use the user's password that is provided in the "create connection" call for the ssl_password. So you can make the ssl_password  the same as the user's password as a solution.

2). If you cannot set the ssl_password to the same as the user's password then you can call setSSLPassword function of TibjmsConnectionFactory object to set the ssl_password for the factory object being looked up:

((TibjmsConnectionFactory)factory).setSSLPassword("password");

3). You can also call the TibjmsSSL.setPassword() function to set the ssl_password before calling createConnection call.

Example:
TibjmsSSL.setPassword(new String("password").toCharArray());

Issue/Introduction

Different ways to pass a ssl_password for the connection factory being looked up from a JNDI server.