Hi, I am facing a problem with SOGo. I am not even sure if it is actually a bug.
When I set SOGoTrustPRoxyAuthentication=YES in /home/sogo/GNUstep/Defaults/.GNUstepDefaults and enable authentication in apache2, it works fine. But if I disable authentication in apache2 leaving SOGoTrustPRoxyAuthentication=YES as it is, I get the message, "Unauthorized" whenever I access SOGo URL.
The reason I need SOGo to work even with apache2 authentication disabled is because I have two apache2 frontend servers running. One is used for connecting via thunderbird and uses GSSAPI authentication (which currently is only possible using Apache2 authentication). The other apache2 frontend is used for the regular SOGo webclient. And for the webclient, popping up browser based prompts for username and password is not clean.
Therefore I would like to know if the following is possible i.e. setting SOGoTrustPRoxyAuthentication=YES and still using the normal SOGo authentication in webclient.
Thanks and Regards, Rahul. -- [email protected] https://inverse.ca/sogo/lists
