Secure Communications

TIBCO API Exchange Gateway supports transport for secure communications between the client requester and the Apache HTTP server.

The transport uses the Secure Sockets Layer (SSL) protocol for exchanging transactions in a secured way. The SSL protocol uses signed digital certificates from a certificate authority (CA) for authentication.

• Mutual SSL Authentication
  When the client sends a request using HTTPs transport, TIBCO API Exchange Gateway supports the authentication of the client based on the digital certificates. This is known as two-way (mutual) SSL authentication.
• SSL Communications Configuration
  This section explains the configuration setup required for SSL communications between the client requester and Apache HTTP server.
• Configure the Apache Server for Basic HTTP Authentication
  To support basic HTTP authentication for a request, you must configure the Apache HTTP server.
• Configure Apache Module for RVRD Setup through a Firewall (DMZ)
  Deployment overview of Apache module in the DMZ setup and other gateway components in a secure network.
• Configure Apache HTTP Server as Reverse Proxy
  Using Apache HTTP Server as Reverse Proxy.

Copyright © Cloud Software Group, Inc. All rights reserved.