Connect to TIBCO Cloud™ Messaging
- Authentication Key
- Server Validation
- How to connect a client application
- The tcm-config.yaml file
- Related Links
TIBCO Cloud Messaging (TCM) uses a publish/subscribe model to provide real-time messaging between mobile, web, and desktop applications. The global communications infrastructure is managed for you through TIBCO Cloud Messaging. As a developer, you can concentrate only on writing the client-side applications. Connections to TIBCO Cloud Messaging are always persistent (durable), secured with TLS (Transport Layer Security), and authenticated with keys managed by you.
Two URLs are provided to you with your subscription to TIBCO Cloud Messaging: one for use with TIBCO eFTL™ and one for use with TIBCO FTL®. The URLs can be obtained from your TIBCO Cloud Messaging home page.
An authentication key is a required argument for your clients to connect to your Cloud Messaging account. The user can create and revoke authentication keys as needed. Use the authentication key when a password is required. Authentication keys can be obtained from your TIBCO Cloud Messaging account page.
NOTE: Revoking a key does not disconnect clients. It only prevents new clients from connecting with the revoked key.
During the TLS handshake, the TIBCO Cloud Messaging server sends clients a server certificate allowing clients to validate the server’s identity.
TIBCO eFTL Server Validation
TIBCO eFTL clients automatically validate the server’s identity using their respective certificate stores of trusted root certificate authorities.
TIBCO FTL Server Validation
TIBCO FTL clients do not automatically validate the server’s identity when they connect. Review the FTL quick start guide of your chosen language for more information on how to implement server validation using PEM trust files.
How to connect a client application
These are the requirements for connecting a client application to TCM. The most important of these are the URL and Authentication Key which are required by both eFTL and FTL clients. FTL has additional requirements.
Connecting a TIBCO eFTL client application
The following values are provided to the eFTL connect call. The various languages differ slightly on how, but in general the URL is given along with an options object. For a specific language, see Quick Start Guides - eFTL.
|URL||Yes||-||The eFTL URL can be obtained from your account page|
|Password||Yes||PROPERTY_PASSWORD||Set to your TCM authentication key|
|Username||Recommended||PROPERTY_USERNAME||Set to your TCM authentication id|
|Client Id||Recommended||PROPERTY_CLIENT_ID||A unique client identifier used for durable subscriptions|
Connecting a TIBCO FTL client application
The FTL sample applications for TCM each include a simple parser that reads a
tcm-config.yaml file which contains all the required values. You can copy this code or use a third party YAML parser. For a specific language, see Quick Start Guides - FTL. The information is used when making an FTL connect call.
|URL||Yes||-||The FTL URL can be obtained from your account page|
|Application||Yes||-||The FTL application name can be obtained from the
|Password||Yes||PROPERTY_STRING_USERPASSWORD||Set to your TCM authentication key.|
|Username||Yes||PROPERTY_STRING_USERNAME||Set to your TCM authentication id.|
|Trust type||Recommended||PROPERTY_LONG_TRUST_TYPE||Set to the FTL constant HTTPS_CONNECTION_USE_SPECIFIED_TRUST_STRING.|
|Trust file||Recommended||PROPERTY_STRING_TRUST_PEM_STRING||Set to your TCM FTL certificate string replacing “\n” substrings with newline characters.|
The tcm-config.yaml file
For each authentication key, TCM provides a YAML file named
tcm-config.yaml to download (look for this icon ). The
tcm-config.yaml file contains all the information needed to connect clients to TCM.
Note: The TIBCO FTL samples require a
tcm-config.yaml in order to run successfully.
|tcm_authentication_key||The connection authentication key. Required to be set as the password by both eFTL and FTL.|
|tcm_authentication_id||A unique identifier associated with tcm_authentication_key. Recommended to be set as the username for both eFTL and FTL when connecting with that key.|
|eftl_url||The URL required for eFTL client connections.|
|ftl_url||The URL required for FTL client connections.|
|ftl_application||The name of the FTL application. Cannot be changed.|
|ftl_certificate||The certificate to verify the authenticity of your FTL servers. Modified to fit on a single line.|