Common Authentication Properties for the CDD File
To avoid conflict with properties used by other components that use authentication, a parallel set of properties (for the TRA and CDD file) is used for MM configuration. These are common authentication properties used in the CDD file.
Property | Notes |
---|---|
java.security.auth.login.config |
|
Provides the absolute location for the login module configuration used by JAAS. Only advanced users should change this value (additional configuration is also needed).
The locations of the provided files are as follows: TIBCO BusinessEvents Decision Manager: BE_HOME/rms/config/security/jaas-config.config TIBCO BusinessEvents Views: BE_HOME/views/config/jaas-config.config TIBCO BusinessEvents Monitoring and Management: BE_HOME/mm/config/jaas-config.config |
|
be.auth.type be.mm.auth.type |
|
Specifies the authentication mechanism. Allowable values are as follows:
file: File-based authentication. Uses a password file. ldap: LDAP-based authentication Uses a pre-existing LDAP setup in use in your environment. Add and configure the properties shown in . Default is file |
|
be.auth.file.location be.mm.auth.file.location |
|
Specifies the absolute filepath to and name of the password file. This file is used for file-based authentication. Each project can have a different file. The locations of the provided files are as follows:
TIBCO BusinessEvents Decision Manager: BE_HOME/rms/config/security/users.pwd. TIBCO BusinessEvents Views: Create a file for each project. A sample file is provided in BE_HOME/examples/views/TickerTracker/config/tickertrackerusers.pwd . TIBCO BusinessEvents Monitoring and Management: BE_HOME/mm/config/users.pwd. |