Hello Am 27.03.2017 um 18:32 schrieb Craig Fisher ([email protected]): > Christian, Hi > > Thanks for the pointers - yes sogo-activesync was installed, and I've turned > up the debug in the sogo.log and the apache.log > > Mar 27 17:07:08 sogod [5979]: |SOGo| starting method 'GET' on uri > '/SOGo/Microsoft-Server-ActiveSync?' > Mar 27 17:07:08 sogod [5979]: |SOGo| traverse(acquire): SOGo => > Microsoft-Server-ActiveSync > Mar 27 17:07:08 sogod [5979]: |SOGo| do traverse name: 'SOGo' > Mar 27 17:07:08 sogod [5979]: |SOGo| do traverse name: > 'Microsoft-Server-ActiveSync' > Mar 27 17:07:08 sogod [5979]: |SOGo| set clientObject: > <SOGo[0x0x5559b85e49c0]: name=SOGo> > Mar 27 17:07:08 sogod [5979]: <0x0x5559bd382640[SOGoActiveSyncDispatcher]> > EAS - Forbidden access for user (null) > Mar 27 17:07:08 sogod [5979]: |SOGo| request took 0.000676 seconds to execute > Mar 27 17:07:08 sogod [5979]: 192.168.205.113 "GET > /SOGo/Microsoft-Server-ActiveSync? HTTP/1.1" 403 0/0 0.002 - - 0 > > Which implies to me that apache (for some reason) isn't getting a username - > which is unsurprising as it doesn’t request any Authorisation. > > [Mon Mar 27 16:07:08.916479 2017] [authz_core:debug] [pid 9790] > mod_authz_core.c(835): [client 192.168.205.113:53478] AH01628: authorization > result: granted (no directives) > [Mon Mar 27 16:07:08.916690 2017] [proxy:debug] [pid 9790] mod_proxy.c(1160): > [client 192.168.205.113:53478] AH01143: Running scheme http handler (attempt > 0) > [Mon Mar 27 16:07:08.916807 2017] [proxy:debug] [pid 9790] > proxy_util.c(2160): AH00942: HTTP: has acquired connection for (127.0.0.1) > [Mon Mar 27 16:07:08.916893 2017] [proxy:debug] [pid 9790] > proxy_util.c(2213): [client 192.168.205.113:53478] AH00944: connecting > http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync? to 127.0.0.1:20000 > [Mon Mar 27 16:07:08.916996 2017] [proxy:debug] [pid 9790] > proxy_util.c(2422): [client 192.168.205.113:53478] AH00947: connected > /SOGo/Microsoft-Server-ActiveSync? to 127.0.0.1:20000 > [Mon Mar 27 16:07:08.917225 2017] [proxy:debug] [pid 9790] > proxy_util.c(2799): AH02824: HTTP: connection established with > 127.0.0.1:20000 (127.0.0.1) > [Mon Mar 27 16:07:08.917319 2017] [proxy:debug] [pid 9790] > proxy_util.c(2965): AH00962: HTTP: connection complete to 127.0.0.1:20000 > (127.0.0.1) > [Mon Mar 27 16:07:08.922994 2017] [proxy:debug] [pid 9790] > proxy_util.c(2175): AH00943: http: has released connection for (127.0.0.1) > > I would have expected the server to request username+password the same way as > it does for autodiscover - but that's done by OCSmanager. I'm assuming that > Sogo does it for EAS and why would it work for normal Sogo requests - but not > EAS requests...? > > What is the process that requests and then handles the HTTP Authorisation > request for username + password? > > Any pointers would be useful. Thanks!! > < cut >
Sorry for the late answer. You try to test ActiveSync via browser. This will not work, because it does not use basic authentication. You need an ActiveSync capable client or a specific test client like EAS-MD http://mobilitydojo.net/2010/03/30/rolling-your-own-exchange-activesync-client/ Beware: It is not easy to use. Be sure to read the documentation. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
