Copyright © TIBCO Software Inc. All Rights Reserved |
This section explains how to select file-based authentication or LDAP-based authentication, and how to configure each authentication option. It assumes that the provided JAAS login module is used. See User Authentication Overview for more background information.You can use a different authentication type and a different password file or LDAP settings for each TIBCO BusinessEvents product that uses authentication. You can actually do so for each engine (processing unit) configured for authentication, but this is not usually needed.
1. In TIBCO BusinessEvents Studio, import and open the relevant project and open its CDD file, as follows:
−
−
−
−
2.
− To configure LDAP authentication, add and configure the LDAP properties shown in Table 47, Authentication Configuration Properties in the CDD File. Familiarity with LDAP is required. Details are not provided in this guide.
For authentication, Active Directory requires the domain name, for example, abc@acme.com, and not distinguished name (which is used with Oracle Directory Server). If you are using Active Directory for authentication, ensure that the userPrincipalName attribute is set on AD server.This procedure continues the instructions in To Enable Authentication and Select File or LDAP Authentication Type.
1. In the CDD file, add (or configure) the property be.auth.file.location and set the value to the location of your password file.For MM authentication use the property: be.mm.auth.file.location
2. Locate and open the password file. Its location is specified in the CDD file. See step 1 for default location details.Do not use spaces. For example here are some entries that might be used in TIBCO BusinessEvents Decision Manager:
• Roles are used for access control (authorization). Access control is used only by TIBCO BusinessEvents Monitoring and Management and TIBCO BusinessEvents Decision Manager. See Chapter 14, Configuring Access Control for a Project.
Copyright © TIBCO Software Inc. All Rights Reserved |