cfmumps.ini
John Willis
< Previous
cfmumps.ini
Next >
The file lib/cfmumps/cfmumps.ini defines several configuration parameters, including administrator panel access, default connector, and connector configuration for a CFMumps instance running within the current document root.
[General]
This section includes instance-wide configuration options not specific to one application or connector.
connector
The connector setting determines which connector technology will be used by this CFMumps instance. ex. lib.cfmumps.connector.GTMJI
connectors
A comma-delimited list of all connectors available in the system.
ex. lib.cfmumps.connector.GTMJI,lib.cfmumps.connector.MWire,lib.cfmumps.connector.CacheExtreme,lib.cfmumps.connector.REST
Connnectors installed on the system but not listed in the connectors setting will not be configurable through the CFMumps Administrator application.
loglevel
Determines the level of detail to be logged by CFMumps itself. Not to be confused with the loglevel settings in the configuration file section for each particular connector. The value of this setting will neither influence nor be influenced by the loglevel settings for installed connectors. Production systems should set this number as low as possible for maximum performance.
Values
| Value | Meaning |
|---|---|
| 0 | None - logging will be disabled |
| 1 | Error - Only errors will be logged |
| 2 | Warning - Only errors and warnings will be logged |
| 3 | Information - Errors, warnings, and informational messages will be logged |
| 4 | Debug - All messages will be logged, including debugging messages |
[lib.cfmumps.connector.GTMJI]
This section configures the CFMumps GTMJI connector.
loglevel
Determines the level of detail to be logged by the GTMJI connector. Production systems should set this number as low as possible for maximum performance.
Values
| Value | Meaning |
|---|---|
| 0 | None - logging will be disabled |
| 1 | Error - Only errors will be logged |
| 2 | Warning - Only errors and warnings will be logged |
| 3 | Information - Errors, warnings, and informational messages will be logged |
| 4 | Debug - All messages will be logged, including debugging messages |
routineoutputpath
The path to be used by the mumps.mEval() API when generating transient routines. Must be a source directory listed in the $gtmroutines environment variable. This is also used in support of inline MUMPS code in CFMumps web pages.
[lib.cfmumps.connector.MWire]
Configures the M/Wire Connector.
host
The host name or network address on which the M/Wire daemon is running.
loglevel
Determines the level of detail to be logged by the M/Wire connector. Production systems should set this number as low as possible for maximum performance.
Values
| Value | Meaning |
|---|---|
| 0 | None - logging will be disabled |
| 1 | Error - Only errors will be logged |
| 2 | Warning - Only errors and warnings will be logged |
| 3 | Information - Errors, warnings, and informational messages will be logged |
| 4 | Debug - All messages will be logged, including debugging messages |
port
The port on which the M/Wire daemon is listening.
password
If the secure setting is set to true, this is the password that will be sent to authenticate M/Wire connections. Note that M/Wire is a clear text protocol, so this password will be transmitted in clear text, which is easily intercepted by malicious man-in-the-middle attacks. It is best to use an stunnel connection to ensure security for the M/Wire protocol.
secure
If true, will use the password setting to authenticate to the M/Wire daemon.
M/Wire Security Note
If you set secure to true, the server on which M/Wire is running must have either the M/Gateway Developments m_apache or MGWSI products installed and configured, as they use these products' implementation of the MD5 hashing algorithm in order to generate and test password hashes.
As MD5 has been considered catastrophically flawed since at least 2004, and subject to both length-extension and collision vulnerabilities, it is no longer considered cryptographically secure, and can be exploited in seconds on a low-powered desktop PC. Therefore, it is recommended that users of the M/Wire protocol encapsulate its traffic in a securely encrypted tunnel, and avoid M/Wire's built-in security implementation altogether.
Even if this usage of MD5 was replaced with a secure hashing algorithm (like SHA-256 or SHA-512), M/Wire messages are transported in clear text unless steps are taken to encapsulate it in a securely encrypted tunnel, so M/Wire security features have little to recommend them.
[lib.cfmumps.connector.REST]
Configures the REST Client connector.
server
The host name or network address on which the server component of the CFMumps REST connector is running.
port
The port number on which the server component of the CFMumps REST connector is listening.
protocol
The protocol (either http or https) to be used when accessing the server component of the CFMumps REST connector.
[administrator]
Configures the CFMumps Administrator application.
password
Contains a one-way hash of the CFMumps Administrator password. Clearing the password setting will cause CFMumps Administrator to prompt the next user who attempts to access the application to create a new password.