Hello Christian, thanks for the reply.
After adding the LDAP clause to my conf and restarting SOGo, I get no further
information in sogo.log. For the record, the ACL entry for the SOGo LDAP user
follows. It’s identical to the permissions in my functional SOGo
implementation, and the DIT is structured the same.
dn: olcDatabase={1}hdb,cn=config
changetype: modify
add: olcAccess
olcAccess: to dn.subtree="ou=Users,dc=tohuw,dc=net" by
dn="uid=sogo,ou=Services,dc=tohuw,dc=net" write
Ron Scott-Adams
[email protected]
“We are stuck with technology when what we really want is just stuff that
works.” (Douglas Adams)
On Feb 25, 2014, at 5:58 AM, Christian Mack <[email protected]>
wrote:
> Hello Ron Scott-Adams
>
>
> Am 2014-02-25 03:53, schrieb Ron Scott-Adams:
>> I'm building a new SOGo install very similar to a current, working one.
>> I'm experiencing an issue with logging in. There is a single auth source
>> (ldap). The error is: "SOGoRootPage Login for user 'username' might not
>> have worked - password policy: 65535 grace: -1 expire: -1 bound: 0"
>> What can I do to elicit more information?
>>
> < cut >
>
> Your config looks OK.
> I guess your user doesn't have the privileges needed on your LDAP.
>
> In order to get more debugging information for your LDAP access, add the
> following to your config:
> LDAPDebugEnabled = YES;
>
>
> Kind regards,
> Christian Mack
>
> --
> Christian Mack
> Abteilung Basisdienste
> KIM
> Universität Konstanz
> --
> [email protected]
> https://inverse.ca/sogo/lists
--
[email protected]
https://inverse.ca/sogo/lists
