It’s also worth mentioning that my postgres database is empty, though the base
schema seems to be present:
sogo=# \d
List of relations
Schema | Name | Type | Owner
--------+----------------------------------+----------+-------
public | sogo_folder_info | table | sogo
public | sogo_folder_info_c_folder_id_seq | sequence | sogo
public | sogo_sessions_folder | table | sogo
public | sogo_user_profile | table | sogo
(4 rows)
Is that normal due to no user having ever successfully logged in, or is
something else wrong that may be contributing to my login issue?
Also, I should mention I also tested logging in as the SOGo ldap user via
ldapwhoami, and it succeeded.
Lastly, everything else in the stack seems to work: Postfix/Dovecot/Sieve
channel a message correctly when testing via Telnet. It’s non-trivial to test
too far beyond that, though, and obviously, this is a login issue specific to
SOGo. I’m sure there’s something simple I’m not considering, but what?
On Feb 25, 2014, at 6:21 PM, Ron Scott-Adams <[email protected]> wrote:
> 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
