Kolab Web Server Integration

Gunnar Wrobel wrobel at pardus.de
Mon May 5 17:53:00 CEST 2008


Lionel NICOLAS <kolab at nividic.org> writes:

> Hi,
>
> Gunnar Wrobel a écrit :
>> Hi Lionel,
>>
>> Lionel NICOLAS <kolab at nividic.org> writes:
>>
>>   
>>> Hi,
>>>
>>> I'm trying to configure VirtualHosts in Apache to access to kolab 
>>> services, like horde.mydomain.com, freebusy.mydomain.com, etc ...
>>>
>>> On my server I've already an Apache2 webserver bound to the 80 and 443 
>>> ports. I've tried to bind the Kolab's Apache on loopback:81, and use 
>>> modproxy_http and modproxy_html to redirect/rewrite requests/responses 
>>> from my frontend Apache2 to Kolab's Apache server ... To improve 
>>> performances, I modified the httpd.conf.template to use non-ssl 
>>> connection on loopback. To sum up, I've tried to do that :
>>>
>>> Client <=> Apache2 [horde.mydomain.com:443] <=> Kolab [127.0.0.1:81/horde]
>>>
>>> I don't manage to make this config work :-s . The primary reason is that 
>>> the rewriting of all the URL and HTML (for example the inclusion of CSS 
>>> and JS) is very complicated, and after few hours of config I concluded 
>>> that it was not possible ... :-)
>>>
>>> Finally, I'm trying to configure my Apache2 to process Kolab's 
>>> horde/freebusy/etc... (so I could shutdown Kolab's Apache). For the 
>>> moment I've fixed some php5 inclusions errors by editing my php.ini. 
>>> I've no php5 warning when I access to the Horde login page, but after 
>>> submitting my login/pass, I've this error :
>>>
>>> *Fatal error*: Call to undefined method Auth_kolab::setAuthError() in 
>>> */kolab/lib/php/Horde/Auth/imap.php* on line *94
>>>
>>> So my question is : Does anyone manage to use Kolab's services in 
>>> Apache2 ? If someboby has a solution for modproxy, I'll be happy too :-p
>>>     
>>
>> Sounds like you are using Kolab-Server-2.1. Is that correct? If that
>> problem is not absolutely urgent for you I'd suggest to wait for the
>> final 2.2 release which is due in about a month. This will come with
>> apache2 which might make things much easier for you.
>>
>> Cheers,
>>
>> Gunnar
>>
>>   
> I'm using Kolabd 2.2rc2.

Then I did misunderstood you. I thought you were still based on
Apache-1. Kolab-Server-2.2-* comes with Apache2 and I think it should
be possible to have the kolab web applications served by an outside
apache.

Your PHP errors sound like they might originate from a discrepancy of
PEAR libraries installed in the outside system and PEAR libraries
installed within Kolab. If you have Horde::Auth from an old version
installed in your outside system and it is higher in your PHP include
path then you are heading for trouble ;)

Cheers,

Gunnar

> It's not urgent, so I think I can wait for the 
> final release ;-)
>
> Thanks,
>
> Lionel.
>>> Thanks.
>>>
>>> --
>>> Lionel
>>> *
>>>
>>> _______________________________________________
>>> Kolab-users mailing list
>>> Kolab-users at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-users
>>>     
>>
>>   
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




More information about the users mailing list