General Horde Settings false PHP Settings E_ALL & ~E_NOTICE 0 true 077 true URL Settings 2 0 1 2 3 $_SERVER['SERVER_NAME'] 30 30 false false rewrite Session Settings Horde true 0 nocache 604800 $_SERVER['SERVER_NAME'] / NOTE: These are only the default values for any database driven backends. You still need to configure the different systems like "Preferences" to actually use a database backend. SQL Database Settings These are the database settings for the traditional relational databases backends (e.g. databases that use SQL to manage its data). NoSQL Database Settings These are the database settings for the NoSQL database backends. These are databases generally optimized for scalability/availability, but do not use a standardized query language to interact with the data. LDAP Settings NOTE: These are only the default values for any LDAP driven backends. You still need to configure the different systems like "Preferences" to actually use a LDAP backend. Authentication Settings true true true false false list list input both imp horde_user false This authentication driver needs manual configuration not possible through this interface. Add the appropriate configuration lines at the end of the generated configuration file. See http://wiki.horde.org/AuthCompositeHowTo for details. localhost 21 true crypt-des aprmd5 crypt crypt-blowfish crypt-des crypt-md5 crypt-sha256 crypt-sha512 md5-base64 md5-hex plain sha smd5 ssha localhost 143 tls none tls ssl false ssha aprmd5 crypt crypt-blowfish crypt-des crypt-md5 crypt-sha256 crypt-sha512 md5-base64 md5-hex msad plain sha smd5 ssha shadowAccount,inetOrgPerson (objectclass=shadowAccount) no 5 30 5 /bin/su php /etc/passwd crypt aprmd5 crypt crypt-blowfish crypt-des crypt-md5 crypt-sha256 crypt-sha512 md5-base64 md5-hex plain sha smd5 ssha false false localhost PAP PAP CHAP_MD5 MSCHAPv1 MSCHAPv2 horde php REMOTE_USER localhost localhost /usr/bin/smbclient ssha aprmd5 crypt crypt-blowfish crypt-des crypt-md5 crypt-sha256 crypt-sha512 joomla-md5 md5-base64 md5-hex mysql plain sha smd5 ssha false mysql mysql mysqli odbc pgsql unix localhost horde horde Some special tokens can be used in the sql query. They are replaced at the query stage:<ul> <li>"\L" will be replaced by the user's login</li> <li>"\P" will be replaced by the user's password</li> <li>"\O" will be replaced by the old user's login (required for update)</li></ul> Eg: "SELECT * FROM users WHERE uid = \L AND passwd = \P AND billing = 'paid'" ssha aprmd5 crypt crypt-blowfish crypt-des crypt-md5 crypt-sha256 crypt-sha512 joomla-md5 md5-base64 md5-hex mysql plain sha smd5 ssha false localhost 143 none none tls ssl mysql mysql odbc pgsql unix 5432 localhost horde horde horde_users user_uid user_pass none ssha aprmd5 crypt crypt-blowfish crypt-des crypt-md5 crypt-sha256 crypt-sha512 md5-base64 md5-hex plain sha smd5 ssha cyrus SSL_CLIENT_S_DN_CN false false 5 5 Terms of Service Agreement Sign Up Settings false true Logging Settings true NOTICE EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG HORDE file /tmp/horde.log true default default false Preferences Settings 65535 Sql uid Alarms Settings Sql 300 Groups Settings Sql cn memberUid false posixGroup,hordeGroup objectclass posixGroup cn memberUid false posixGroup,hordeGroup objectclass posixGroup Permissions Settings Sql Shares Settings Shares are objects or lists that can be shared with other users, e.g. calendars that other users can be given read or write access to. Allow Sharing? false true true false false Share Caching Enabling share caching improves performance because the share backend will only be queried once per session. But it also increases the users' session sizes, and share changes won't take effect before the users log in the next time. false Shares Driver You can use different driver types for the Horde Share system. The default driver is the SQL-NG driver. Sqlng Kolab Sqlng Sql Caching Settings 86400 File APC is not recommended for general purpose caching as it is not persistent and the size of the cached data for even a small installation (25+ users) will likely exceed the default APC storage size. 0 SQL is not recommended for caching as the overhead required to store/retreive the data cancels much of the benefit of caching. xCache is not recommended for general purpose caching as it is not persistent and the size of the cached data for even a small installation (25+ users) will likely exceed the default xCache storage size. CSS Caching CSS caching packages all stylesheets used in a page into a single file sent to the browser. It also allows compression and optimization of this file to reduce the data size. Caching reduces server load, speeds up the user's browsing experience, and is HIGHLY RECOMMENDED. false true For filesystem caching to work, the "static" directory in the horde base must be writable by the user the web server is running as. If running Horde in a cluster (or behind a single web frontend), to use filesystem caching it is best to have every PHP backend server have access to a shared drive that is visible and mounted to the "static" directory on the web frontend. (NOTE: if you manually change the CSS files, you will need to manually delete the cached CSS static files to see the changes.) Requires a configured Horde caching backend. This method is STRONGLY DISCOURAGED. Browsers will likely cache this data and ignore updates, even though we append a "cache-busting" unique version parameter to the URL. You almost certainly want to use 'filesystem' instead. false 86400 Javascript Caching Javascript caching packages all static javascript files used in a page into more efficient chunks to send to the browser. It also allows compression and optimizations of this file to reduce the data size. Caching reduces server load, speeds up the user's browsing experience, and is HIGHLY RECOMMENDED. false true For filesystem caching to work, the "static" directory in the horde base must be writable by the user the web server is running as. If running Horde in a cluster (or behind a single web frontend), to use filesystem caching it is best to have every PHP backend server have access to a shared drive that is visible and mounted to the "static" directory on the web frontend. Requires a configured Horde caching backend. This method is STRONGLY DISCOURAGED. Browsers will likely cache this data and ignore updates, even though we append a "cache-busting" unique version parameter to the URL. You almost certainly want to use 'filesystem' instead. php /opt/java/jre/bin/java -c /opt/java/jre/bin/java 604800 Theme Caching Theme caching optimizes display of themed elements. Caching reduces server load (specifically by dramatically reducing filesystem access), and is HIGHLY RECOMMENDED. Requires a configured Horde caching backend. false appversion The theme cache will be updated only when a new Horde version is installed. This is the RECOMMENDED setting for most installations. The theme cache is never checked for consistency. Once created, it will be used until the cache entry expires. 604800 Locking Settings Sql Tokens Settings Sql History Settings Sql DAV Settings Sql Mailer Settings sendmail /usr/lib/sendmail -oi tls none tls ssl false SMTP Authentication requires a TLS connection. There is no need to configure the secure connection as it is always used by Horde. true true false Virtual File Storage Settings Session Handler Settings Unless you are running Horde on a PHP cluster, there is NO reason to use any session handler backend other than Builtin (i.e. session data stored on local filesystem). Builtin If you have configured a custom session extension in php.ini (such as native memcache sessions) then you should use this option. Horde doesn't force PHP to use the file-based session handler, so your php.ini settings settings will be deferred to. /tmp/ false false HTTP Proxy Settings If you need to use a proxy for fetching HTTP resources (feeds, security keys, external calendars or free/busy information, etc.), configure it here. Spell Checker Settings GnuPG Settings pool.sks-keyservers.net pool.sks-keyservers.net subkeys.pgp.net pgp.mit.edu 10 OpenSSL Settings Theme Settings false Image Manipulation Settings false Image Metadata Driver Settings Bundled MIME Detection Settings Country Lookup Settings Timezone Lookup Settings ftp://ftp.iana.org/tz/tzdata-latest.tar.gz Problem Reporting Settings false array() webmaster@example.com example.com true Menu Settings all all authenticated never authenticated all authenticated never all all authenticated never all all never authenticated authenticated never all all never authenticated authenticated never Portal Blocks Settings Fortune Configuration Account Info Configuration null /usr/bin/quota /bin/grep false /etc/mtab /usr/bin/finger uid false This will use the parameters set in the Kolab Groupware Server tab. You must enable Kolab integration for this to work. uid false User Capabilities and Constraints false true basic dynamic mobile smartmobile API Keys Settings Facebook Integration Settings If you want to allow your users to interact with their Facebook profiles, and you've set up the necessary settings on Facebook, you can enter the key and secret here. See http://wiki.horde.org/Doc/Admin/Config/Horde/Facebook for details. false Twitter Integration Settings If you want to allow your users to interact with their Twitter account, enable this section. You must setup an application on Twitter and obtain the OAuth secret and key from Twitter. See http://wiki.horde.org/Doc/Admin/Config/Horde/Twitter for details. false Url Shortening false TinyUrl Weather Services If you want to provide weather information to your users you must select a provider and provide your API keys. false 21600 1 1 2 21600 IMAP Server Settings If you intend to store user data like shares and groupware data on an IMAP server then you will need to ensure that the following fields correspond to your IMAP server setup. The IMAP groupware storage will use version 2 of the Kolab XML format. See http://wiki.kolab.org/Kolab_Format_Intro for details. false IMAP Server Settings localhost 143 tls none tls ssl example.com true IMSP Server Settings If you plan to use any of Horde's IMSP server support, enable this option and configure the server settings below. Note that you must still configure/enable specific IMSP support in the appropriate section. false IMSP Server Settings localhost 406 Plaintext /tmp/ /cyrus/usr/cyrus/bin/imtest LOGIN gssapi Kolab Server Settings *** IF YOU HAVE NO IDEA WHAT KOLAB IS THEN YOU CAN SAFELY IGNORE THIS TAB *** Kolab is in no way required for normal Horde usage. If, however, you intend to use Horde as a webclient for Kolab then you will need to ensure that the following fields correspond to those required by your Kolab installation. You can find some of the required values in the <code> $KOLAB_ROOT/etc/kolab/kolab.conf</code> configuration file. Please note that the old iCal/vCard storage format has been dropped in favour of the new XML storage format & IMAP folder annotations; subsequently the Horde Kolab modules will only work with version 2 of the Kolab server. If you would like to find out more about Kolab then please visit the Kolab community website at http://www.kolab.org/ false Kolab LDAP Server Settings localhost 389 dc=example,dc=com cn=nobody,cn=internal,dc=example,dc=com Kolab Cyrus IMAP Server Settings localhost 143 2000 example.com true Kolab SMTP Server Settings localhost 25 Kolab Free/Busy Application Settings Enter the leading part of the URL to the Kolab Free/Busy application here. This will usually be "https://localhost/freebusy" but if you installed it so that you reach the application at "https://freebusy.example.org" then you would enter "https://freebusy.example.org". The URL "https://freebusy.example.org/freebusy" would thus need the setting "https://freebusy.example.org/freebusy". https://localhost/freebusy A distributed hash table is a way of sharing data across multiple servers by associating a piece of data with a static key. It is useful for cache-like operations, since it is usually much faster to set and retrieve the data from the hash table than the underlying data storage driver. none localhost 11211 false false 0 true tcp localhost 6379 none mymaster false The use of ActiveSync in the United States is PROHIBITED due to patent issues. If you are NOT in the United States, or you have a license to use ActiveSync, you may enable ActiveSync below and create an alias on your webserver to redirect /Microsoft-Server-ActiveSync to /horde/rpc.php. See http://wiki.horde.org/ActiveSync for more information. Please note that History system needs to be enabled too. false Storage ActiveSync needs to store information about device properties and state data such as syncronization keys and hierarchy data. Choose the storage backend to use. Sql Capabilities true 14.1 2.5 12 12.1 14 14.1 Authentication ActiveSync can be configured to authenticate against Horde using either HTTP Basic authentication, X509 client certificates, or both. HTTP Basic will authenticate the credentials passed from the client against the configured Horde authentication backend. If client certificates are used you will need to properly configure your webserver for this as well as provide some mechanism for using hordeauth with the IMAP server. See http://wiki.horde.org/ActiveSync for more details on client certificate authentication. If selecting both basic and client certificates, make sure you are not already using client certificate authentication in Horde; if client certificates are used for general Horde authentication then they must be used here as well. If unsure, select Basic. basic SSL_CLIENT_S_DN_CN SSL_CLIENT_S_DN_CN Autodiscovery full user hook Logging false protocol 2 1 Ping Settings The Heartbeat Interval specifies the length of time, in seconds, that the server SHOULD wait before notifying the client of changes in a folder on the server. These settings allow you to indicate the allowable range for this setting. Note that not all clients will request this information. NOTE: Some Android devices do not implement this correctly. If you plan on synching Android devices, you should make sure that this range is wide enough to allow Android's default of 470 seconds. true 60 2700 480 60 15