On 13-06-26 11:24 AM, Terry Welch wrote:
Thanks for the quick reply. I fixed the bindDn to where I no longer get the
Invalid credentials error, but in my sogo.log file it still says:
192.1.1.237 - - [26/Jun/2013:01:26:13 GMT] "GET /SOGo/ HTTP/1.1" 302 0/0 0.164 -
- 5M
192.1.1.237 - - [26/Jun/2013:01:26:13 GMT] "GET /SOGo/user HTTP/1.1" 302 0/0
0.003 - - 40K
192.1.1.237 - - [26/Jun/2013:01:26:13 GMT] "GET /SOGo/user/view HTTP/1.1" 302
0/0 0.004 - - 16K
SOGo is returning a 302 redirect when you hit /SOGo/user/view and then there's
nothing else. Can you check to which URL sogo tries to redirect the browser?
You could either use browser based tools to do this, or dump the http traffic
sent from sogo (tcpflow -c -i lo src port 20000)
--
users@sogo.nu
https://inverse.ca/sogo/lists
