Configuration files

There are two configuration files used that control how the database is accessed and used, and how you can login to the system.


This file has the database configuration stored. A sample can look like this.



The mysql_ variables are set so it can connect to the database. How much the user and password is used depends on the login configuration, it can range from accessing the user records and nothing more to having access to the full database. The server settings are used for inserts in the database, all generated keys will be between the min and the max values. The current value is stored in the aseqno table to keep track of what's being inserted. The id must correspond to the MySQL database server ID. This is to allow several servers to be running in distant locations with replication between them to keep it all in sync.


This file has some base configuration to do with how users are authenticated.

                    array("ldap"=>array(0=>array("description"=>"Local LDAP",
                                        1=>array("description"=>"Enterprise LDAP",
                          "imap"=>array("description"=>"Local Imap",
                          "spotsql"=>array("description"=>"Local DB",

There are three methods to connect to the database. "dbAuth" uses the login/password to connect directly to the database. That way the access can be set for each user to exactly what is needed. "internal" uses the login/password supplied in the file to get a connection to the database. "fixedAuth" connects using the login of the user, but a password stored in the user table. "internal" and "fixedAuth" is useful if you're using a secondary system to validate users.

The module_setup variable holds the different methods of authentication that will be used in sequence. If the type holds an array, the same module will be used several times with different configuration.