Yes, you are correct. That was causing the issue. Thank you very much for the assistance. The only thing I need help with now is understanding how SOGo's resource scheduling stuff works, as well as the document sharing.
Thanks again, -- Michael Crilly Comtek IT Systems Administrator E: michael.cri...@comtek.co.uk http://www.comtek.co.uk/ On Tuesday, February 15, 2011 15:27 GMT, Francis Lachapelle <flachape...@inverse.ca> wrote: > Hi Michael > > On Feb 15, 2011, at 9:44 AM, michael.crilly wrote: > > > { > > CNFieldName = cn; > > IDFieldName = cn; > > UIDFieldName = cn; > > baseDN = "ou=groups,dc=tld,dc=co,dc=uk"; > > bindDN = "cn=user,ou=some_ou,dc=tld,dc=co,dc=uk"; > > bindPassword = super_secret; > > canAuthenticate = NO; > > filter = "(accountStatus=active)"; > > hostname = tld.co.uk; > > id = public; > > isAddressBook = YES; > > port = 389; > > type = ldap; > > } > > )' > > > > The first resource worked fine as an authentication resources, but once I > > added the second resource, it stopped working. Any ideas? Are there any > > other SOGo configuration flags I am missing, perhaps? > > Set canAuthenticate to YES, even though your groups certainly has no > credentials. > > Also use a distinctive id for this second source ("public" is already used by > your first source). > > 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 -- users@sogo.nu https://inverse.ca/sogo/lists
