> SSL Authentication Only
> EMS servers can use SSL for secure data exchange (standard usage), or only for client authentication. This section describes the use of SSL for client authentication.
> Motivation
> Some applications require strong or encrypted authentication, but do not require message encryption.
> In this situation, application architects could configure SSL with a null cipher. However, this solution incurs internal overhead costs of SSL calls, decreasing message speed and throughput.
> For optimal performance, the preferred solution is to use SSL only to authenticate clients, and then avoid SSL calls thereafter, using ordinary TCP communications for subsequent data exchange. Message performance remains unaffected.
> Preconditions
> All three of these preconditions must be satisfied to use SSL only for authentication:

> ● | The server and clients must both be release 4.2 or later. (If not, EMS behavior reverts to using SSL for all communications throughout the life of the connection.)

> ● | The server must explicitly enable the parameter ssl_auth_only in the tibemsd.conf configuration file.

> ● | The client program must request a connection that uses SSL for authentication only. clients can specify this request in factories by enabling the ssl_auth_only parameter, or by calling:

> − | Java: TibjmsSSL.setAuthOnly

> − | C: tibemsSSLParams_SetAuthOnly

> − | C#: EMSSSL.SetAuthOnly

> See Also
> ssl_auth_only on page 201

Copyright © TIBCO Software Inc. All Rights Reserved.