Hi On 2012-06-04, at 6:57 AM, Николай Клименко wrote:
> sogo Version 2.0.0 > Authorization is in Active Directory > > Changing CN attribute, the user won’t get authorization till sogo daemon is > started on. > > Authorization attempt > Jun 03 21:05:48 sogod [10192]: SOGoRootPage Login for user 'test_user' might > not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0 > 10.8.0.6 - - [03/Jun/2012:21:05:48 GMT] "POST /SOGo/connect HTTP/1.1" 403 > 34/59 0.003 - - 0 > > After daemon restart – authorization is on > Jun 03 21:07:12 sogod [10562]: SOGoRootPage successful login for user > 'test_user' - expire = -1 grace = -1 The DN is cached in memory. If you change a CN, your only option is to restart sogod (and memcached). You can fill a bug report if you want (http://sogo.nu/bugs). Thanks, Francis -- flachape...@inverse.ca :: +1.514.755.3640 :: http://www.inverse.ca Inverse :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
