Please, do not bother answering that. I managed a work around that I am not sure if I have seen somewhere else, but here it is:
For the entry on the remote authentication server, I have created another one, with the same uid, on the local LDAP server (residing on the sogo server). So, the server seeks for a specific schema and it finds it. That's all it needs to know apparently, for I only created the local LDAP entry using only the MUST fields (uid, sn, cn). Password and owner CN are checked against the (remote) authentication server. Problem would be to create an entry for every one on the remote LDAP, but this can be scripted... To end this, I would like to elaborate a bit on the error I described here below. The remote LDAP did bind, it did not however search, for it was requested for a series of fields that were not present (something like SEARCH attr=[an endless list]), providing thus an error (status 101). On Thu, Dec 8, 2011 at 12:54 PM, Stavros Souvatzis <[email protected]> wrote: > Having read the documentation, I am trying to find if there is any kind of > possibility for the following. > > Our Authentication server (LDAP - Open LDAP) has a users group where mail > field has not been set as attribute to users. We already have over 3.500 > records. > > SOGo needs(?) to lookup the mail address in the LDAP database, using the > MailFieldNames declaration in the .GNUstepDefaults file. > > The only way that I could manage to declare the mail address for any user, > without altering the existing format of our LDAP server, would be like that: > uid (field) + @domain.com (string) > that would not be wrong in fact, because this is exactly how the mail > addresses are formed. > > Is there a way to do that, either in the .GNUstepDefaults file or by any > other means, like for instance, mangling the code or some conf file? > > Thanks. > -- [email protected] https://inverse.ca/sogo/lists
