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. This configuration can be with EMS .conf or .json configuration files.
Note: The document only covers EMS utilizing OAuth 2.0. FTL OAuth 2.0 for authentication is
not supported when EMS is used with FTL stores.
-
2
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now