Secure Communication Channels

All TIBCO BPM Enterprise communication must be carried out through secure communication channels. The channels must be secured by a combination of authenticated and authorized access and encryption of data.

By default, some communication channels are not secure. However, they can be secured by configuring the channels to use either HTTPS or TLS.

The following diagram illustrates the basic TIBCO BPM Enterprise communication channels: 

The following table describes the communication channels, configuration details, along with the references for additional information:

Flow

Communication Channel

Configuration

Description

A

Web client - Load balancer

Configure the load balancer to use HTTPS.

 

This is the communication from the client's browser to the load balancer or ingress controller that is used by the hosting Kubernetes system. 

For details, see the documentation for your external load balancer or ingress controller.

B

TIBCO BPM Enterprise uses SMTP server with TLS

This is done by configuring an SMTP shared resource.

The configuration to establish communication with the SMTP server used by TIBCO BPM Enterprise.

For details, see TIBCO® BPM Enterprise Administration.

C

TIBCO BPM Enterprise Database with TLS

 

This is the database connection configuration used by TIBCO BPM Enterprise.

For details, see TIBCO® BPM Enterprise Installation.

D

TIBCO BPM Enterprise uses LDAP with TLS

 

This is the connection configuration for the required LDAP server used by TIBCO BPM Enterprise.

For details, see TIBCO® BPM Enterprise Installation.