Update configuration files#


These instructions refer to older versions of HRM!

3.7 to 3.8#

HRM 3.8 brings a few simplifications in the configuration files. Please run the following commands:

cd $HRM_HOME/config
cp -p hrm_server_config.inc hrm_config.inc


The following files have become redundant and can be removed:



If you are upgrading from an older version of HRM and both files had the same content, you can simply rename one of them to hrm_config.inc.

3.6 to 3.7#

There were no changes in the configuration files between versions 3.6 and 3.7 of HRM.

3.5 to 3.6#

There were no changes in the configuration files between versions 3.5 and 3.6 of HRM.

3.4 to 3.5#

There were no changes in the configuration files between versions 3.4 and 3.5 of HRM.

3.3 to 3.4#


The support for various authentication mechanisms was extended in HRM 3.4. This comes with a change in configuration: the $authenticateAgainst variable is now an array and its values have also changed (although, temporarily, the old ones are still supported). Example:

$authenticateAgainst = array("active_dir", "integrated");


The configuration variable $useDESEncryption (that was not used) must be removed from the configuration files!


Please follow these instructions first if you are upgrading from older versions.

3.2 to 3.3#

The $change_ownership option is not supported in version 3.3 any more. If the variable is present in the configuration files hrm_{server|client}_config.inc it will be silently ignored. For consistency reasons it is therefore recommend to remove this setting from the config file(s).

Group authentication#

As of HRM 3.3, external authentication via Active Directory or generic LDAP now supports group authorization. An additional array $AUTHORIZED_GROUPS can be set to define the set of Active Directory or generic LDAP groups that are granted access to HRM.

3.1 to 3.2#

As of version 3.2 of HRM, the system users running the Queue Manager and the web server are expected to have direct read-write access to the data folders. If this is not the case for your setup and you rely on adding the web server user to /etc/sudoers, please notice that this behavior is deprecated in 3.2 but can still be enabled by adding:


in hrm_{server|client}_config.inc. The variable $change_ownership defaults to false if not explicitly set to true in the configuration, in compliance to the new behavior.


As of HRM 3.3, this variable will be ignored and the new behavior will be enforced!

3.0.x to 3.1#

No changes in the configuration files.

2.1.x to 3.0#

From HRM 2.1.x to HRM 3.0, one variable was added in the configuration files.


1.2.x to 2.0#

From HRM 1.2.x to HRM 2.0, three variables were added in the configuration files:

[+] max_upload_limit
[+] max_post_limit
[+] email_list_separator

Moreover, three variables were removed:

[-] resultImagesOwnedByUser
[-] resultImagesRenamed
[-] enable_code_for_huygens


If you are upgrading straight from HRM 1.2.x, please notice that as of HRM 2.0 configuration and sample files were moved as per following table.

Config files (new)

Sample files (new)

Config files (1.x)

Sample files (1.x)