Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Setting Up Legacy ActiveSpaces Cluster Security and Authentication

When security is used, any transmission of messages within the Legacy ActiveSpaces cluster occurs on a secure transport. A security domain's transport security setting controls the level of security used for communication within the Legacy ActiveSpaces cluster.

Before you beginEnsure that the cluster provider is set to Legacy ActiveSpaces, see Setting Up Legacy ActiveSpaces as Cluster and Cache Provider. Also, ensure that the cluster is set to use TCP-based discovery Legacy ActiveSpaces Cluster Discover URL.

Procedure
1. Start TIBCO BusinessEvents with a non-secure Legacy ActiveSpaces cluster.
   To enable security for the Legacy ActiveSpaces cluster, you first have to configure the cluster to use TCP-based discovery (it cannot use multicast discovery).
2. Create a security policy and security token file by using the Legacy ActiveSpaces admin utility. Ensure that there is a `metaspace_access` entry with the cluster name specified in the CDD file. For details, see TIBCO ActiveSpaces version 2.x Documentation.
3. Shut down the cluster.
4. Open the project CDD file for editing.
5. Each processing unit (PU) is either a Controller or a Requester. You can change its role on the Processing Unit tab using the be.engine.cluster.as.security.mode.role property to Requestor or Controller. settings. By default, TIBCO BusinessEvents assumes all nodes to be requesters. However, every cluster must have at least one controller node.
   By default, all PUs are requesters so at least one PU in the cluster needs to be a controller. You can override the cluster level controller or requester settings in the PU by checking the Override checkbox and specifying a value. In most cases, you would only need to override the key file paths.
6. On the Cluster tab, select the Security Enabled checkbox for the Object Management, to enable the security.
7. Based on the role of PU as Controller or Requestor update their security settings: Supply the security file based on the security with the following properties in the CDD:
   For the Controller, specify the path of a security policy file and the password for its key in the Policy File and Policy File Identity Password fields.
   For the Requestor, specify the path of the security token file and the password for its key in the Token File and Token File Identity Password fields.

   Requester settings are dependent on the authentication policy defined in the controller's policy file.

   - If the authentication type in the policy file is "userpwd" and the authentication source is "system" or "LDAP", specify Username and Password. You might also need to specify Domain, if the authentication source is "system".
   - If the authentication type in the policy file is "x509", which means that the authentication source is an LDAP configured with certificate-based authentication, then specify LDAP Identity File andPassword (in this case the password is for the private key in the identity file).

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.