1 = Web Server Integration = 2 3 Although imip-agent is mostly concerned with e-mail messaging, it can 4 integrate with a Web server for the following purposes: 5 6 * To [[../FreeBusyPublishing|publish free/busy information]] for calendar users 7 * To provide a [[../CalendarManager|management interface]] for calendar users 8 9 Currently, imip-agent provides configuration files for Apache, but other Web 10 servers may also be supported. 11 12 == Authentication and Access Control in Apache == 13 14 Apache supports a range of mechanisms for protecting resources and 15 authenticating users. Most usefully for imip-agent given the 16 [[../MailIntegration|e-mail integration]] requirements, modules supporting 17 [[http://httpd.apache.org/docs/2.4/mod/mod_authnz_ldap.html|LDAP]] and 18 [[http://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html|text-based lists]] 19 of users are available for such purposes. 20 21 == Configuring Web Servers for Free/Busy Publishing == 22 23 Each user may request the [[../FreeBusyPublishing|publishing]] of their 24 free/busy information by configuring certain settings. The 25 `conf/apache/imip-agent.conf` file provides a configuration file for 26 deployment with the Apache Web server software that exposes a directory for 27 Web publishing containing the published free/busy information. 28 29 Access to free/busy information may not be moderated, but Web server 30 directives can be introduced to impose access controls. Mail programs that 31 wish to consult the free/busy information may have problems in dealing with 32 authentication mechanisms, however, and it may be regarded as acceptable in 33 certain environments to expose such information publicly or with 34 network-specific access constraints. 35 36 == Configuring Web Servers for the Calendar Management Interface == 37 38 A [[../CalendarManager|calendar management interface]] is provided to allow 39 users to view and interact with their calendars through the Web. The 40 `conf/apache/imip-manager.conf` file provides a configuration file for 41 deployment with the Apache Web server software that enables this interface. 42 43 The management interface is deployed as a CGI program, meaning that a suitable 44 module must be enabled in the Apache configuration. On Debian, this is done as 45 follows: 46 47 {{{ 48 a2enmod cgi 49 }}} 50 51 Since such access to calendars should only be performed by identified 52 users, access controls are suggested in the configuration file. Modules 53 providing additional authentication support may need to be enabled. For 54 example, on Debian, the LDAP authentication/authorisation support is enabled 55 as follows: 56 57 {{{ 58 a2enmod authnz_ldap 59 }}}