Guest
Welcome login


TIBCOmmunity > Products > Messaging > Enterprise Message Service > Conversations
Home   Members Communities
Conversations () Resources () Blogs ()

Enterprise Message Service

Up to Conversations in Enterprise Message Service

This Question is Possibly Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)

Security between .net client and EMS server

Created on: Feb 9, 2010 2:38 AM

My team is planning to use EMS as transport for transferring messages between applications.

The applications are a mix of .net and java applications. What are the options available to implement security between the clients and the EMS server.

I need something that will work for both .net and java clients.

EMS documentation says SSL is not supported by .net API.

The next option is to use LDAP, but for LDAP authentication we need to pass the userid and password from the client api when creating the connection to EMS server and in the absence of SSL for .net api we do not want the user id/password floating around.

Is there anything else we can do that will work for both java and .net api clients. Any help is appreciated. Thanks.

Click to view Carlo Milono's profile Enthusiast 449 posts since
Apr 29, 2008
1. Feb 18, 2010 2:11 PM in response to: Irfan
Re: Security between .net client and EMS server

Current versions of EMS support SSL for .NET (e.g., from 5.1 docs):

 

General Setup

 

When a EMS .NET client establishes an SSL connection to the EMS server, it should at the very least specify the TARGET_HOST_NAME parameter, this is a required parameter for the SSLStream. A client then has to specify one of the certificate store typesEMSSSL_STORE_TYPE_FILE or EMSSSL_STORE_TYPE_SYSTEM along with the STORE_INFO object. The Store info has all the required information:

 

  • In case of the system store, the store info has information about the location of the store, the store name and the certificate name to look for in the store.
  • In case of the file store, the store info has information about the the client identity, the password for the private key and any optional trusted certs.


More Like This

  • Retrieving data ...