Re: [SOGo] One user cannot log in...

2011-08-22 Thread Bruce Johnson

On Aug 20, 2011, at 12:49 PM, Jason Wohlford wrote:

 Pardon! Wrong command!
 
  defaults write sogod SOGoCacheCleanupInterval 0
 
 On Aug 20, 2011, at 2:46 PM, Jason Wohlford wrote:
 
 
 On Aug 20, 2011, at 2:25 PM, Bruce Johnson wrote:
 
 We have SOGo set up using our Active Directory domain for the ldap source, 
 and one user cannot log in. I get the message:
 
 SOGoRootPage Login for user 'username' might not have worked - password 
 policy: 65535  grace: -1  expire: -1  bound: 0

Nope, didn't fix it.

-- 
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs


-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] One user cannot log in...

2011-08-22 Thread Bruce Johnson
Dropping her AD account and re-adding it seems to have fixed the issue. I don't 
know why.

-- 
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs


-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] One user cannot log in...

2011-08-20 Thread Bruce Johnson
We have SOGo set up using our Active Directory domain for the ldap source, and 
one user cannot log in. I get the message:

SOGoRootPage Login for user 'username' might not have worked - password 
policy: 65535  grace: -1  expire: -1  bound: 0

in the sogo.log.

This person has no problems logging in to any other service in the domain, and 
her AD record doesn't look any different than any other. 

All I've found searching the list is 'this is LDAP configuration issues'; we 
haven't run into any other person on the domain with this issue.

Any ideas?

-- 
Bruce Johnson

Wherever you go, there you are B. Banzai,  PhD

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] One user cannot log in...

2011-08-20 Thread Jason Wohlford

On Aug 20, 2011, at 2:25 PM, Bruce Johnson wrote:

 We have SOGo set up using our Active Directory domain for the ldap source, 
 and one user cannot log in. I get the message:
 
 SOGoRootPage Login for user 'username' might not have worked - password 
 policy: 65535  grace: -1  expire: -1  bound: 0
 
 in the sogo.log.
 
 This person has no problems logging in to any other service in the domain, 
 and her AD record doesn't look any different than any other. 
 
 All I've found searching the list is 'this is LDAP configuration issues'; we 
 haven't run into any other person on the domain with this issue.
 
 Any ideas?


I ran into a similary problem using OpenLDAP. However, it wasn't related to 
just one user, it would occur on all users. What I did to fix the error on my 
side was the following command:

  defaults write sogod SOGoLDAPQueryTimeout 30

My hope is that will fix your issue too. I suspect a bug in the caching 
mechanism for SOGo.

Best Regards,
Jason

-- 
Jason Wohlford
ja...@wohlfordcompany.com
http://www.wohlfordcompany.com/
334.322.1491

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] One user cannot log in...

2011-08-20 Thread Jason Wohlford
Pardon! Wrong command!

  defaults write sogod SOGoCacheCleanupInterval 0

On Aug 20, 2011, at 2:46 PM, Jason Wohlford wrote:

 
 On Aug 20, 2011, at 2:25 PM, Bruce Johnson wrote:
 
 We have SOGo set up using our Active Directory domain for the ldap source, 
 and one user cannot log in. I get the message:
 
 SOGoRootPage Login for user 'username' might not have worked - password 
 policy: 65535  grace: -1  expire: -1  bound: 0
 
 in the sogo.log.
 
 This person has no problems logging in to any other service in the domain, 
 and her AD record doesn't look any different than any other. 
 
 All I've found searching the list is 'this is LDAP configuration issues'; we 
 haven't run into any other person on the domain with this issue.
 
 Any ideas?
 
 
 I ran into a similary problem using OpenLDAP. However, it wasn't related to 
 just one user, it would occur on all users. What I did to fix the error on my 
 side was the following command:
 
  defaults write sogod SOGoLDAPQueryTimeout 30
 
 My hope is that will fix your issue too. I suspect a bug in the caching 
 mechanism for SOGo.


-- 
Jason Wohlford
ja...@wohlfordcompany.com
http://www.wohlfordcompany.com/
334.322.1491

-- 
users@sogo.nu
https://inverse.ca/sogo/lists