How to Setup TIBCO Enterprise Message Service with OAuth 2 for Authentication

TIBCO Enterprise Message Service (EMS) now supports authentication of client connections via

OAuth 2.0.

EMS clients require an access token to connect to an EMS server configured with OAuth 2.0

authentication. Additionally, an EMS server itself may require an access token to connect to

another EMS server or a TIBCO messaging product that is configured for OAuth 2.0

authentication.

The purpose of the document is to provide a guide to configure, and run a simple TIBCO

Enterprise Message Service (EMS) in a fault-tolerant configuration utilizing OAuth 2 for

authentication.

Note: The document only covers EMS utilizing a shared file system for storage. Once FTL

support OAuth 2.0 for authentication, this document will be updated to outline that configuration.

How_to_oauth2_in_EMS.pdf