Legacy ActiveSpaces Cluster Transport Security

Transport-level security allows you to protect data being transported within the cluster by preventing alteration of traffic, eavesdropping, and exchange of data between untrusted parties.

The available settings for transport_security are:

encrypted_normal 
 Use secure transport with 128 bit symmetric key encryption (default).
encrypted_strong
  Use secure transport with 256 bit symmetric key encryption.
integrity
  Use secure transport without encryption.

The two possible node types in a secure Legacy ActiveSpaces cluster are:

Controllers
Nodes dedicated to enforcing a security domain's defined security behavior for a cluster associated with the security domain. Security domain controllers are the only discovery nodes in a cluster.
Requestors
Nodes that require access to the data in the cluster, such as a seeder or a leech, and which need to be authorized by a controller. Requestors can never be used a discovery nodes.

Authentication

The controller nodes or processing units are configured with a security policy file. The requester nodes or processing units provide a token file and additional credentials to the controller for authentication. The controller performs authentication as defined in its policy file and using the credentials provided by the requester.

For details on security and authentication in Legacy ActiveSpaces, see TIBCO ActiveSpaces version 2.x Documentation.