Authentication Options
You can choose between file-based and LDAP user authentication.
- File-Based Authentication
- This method authenticates a user against user data stored in a file-based repository. This method is not recommended for production purposes. In file-based authentication, define a list of user names, passwords, and roles in the file (default) users.pwd file. This file is commonly referred to as the password file.
- LDAP Authentication
- This method authenticates users against a directory server using LDAP as a protocol. TIBCO BusinessEvents applications can leverage this information to authenticate users. The role information is configured through an LDAP attribute like the nsroledn attribute in Oracle Directory Server. The LDAP attribute differs in different directory server products. The details of configuring LDAP authentication are beyond the scope of this documentation. Consult your LDAP product documentation.
Authentication In Various Components
Authentication is used in components of various TIBCO BusinessEvents products:
- TIBCO BusinessEvents Monitoring and Management
- JMX MBeans authentication is available but not enabled by default. You can enable it using a JMX property in the be-engine.tra file. See Authentication Configuration for instructions.
- TIBCO BusinessEvents Decision Manager RMS Component
- File-based authentication is enabled by default for the TIBCO BusinessEvents Decision Manager RMS component and LDAP authentication is supported.
- TIBCO BusinessEvents Views
- Authentication is available but not enabled by default. The following TIBCO BusinessEvents Views example project is configured for file-based authentication: BE_HOME/examples/views/TickerTracker.
Copyright © Cloud Software Group, Inc. All rights reserved.