[SOGo] Why not use Samba4 as LDAP?
Hi, I am going through documentation and doing test setups (many) for a while to be able to use Sogo's native outlook connection feature. My problem is not mainly for the setup or configuration but to figure out the best suitable underlying architecture. The documentation says Samba4 is required for native outlook support, if an ldap server or AD is in-place as a user directory the sync scripts are not provided and also says Samba4 can act as an ldap server. If I am starting from scratch, why would I bother with a separate ldap server, since Samba4 is sort of an ldap server and a requirement anyway. Right? I guess not. I have checked Sogo's ZEG and a separate ldap server is implemented. I have also took a quick look at Zenytal Server 3.3, which includes sogo and openchange in order to provide native outlook connection feature and they have also implemented a separate ldap server as well. Now I am wondering what could I have been missing? Why would I want to go with an additional ldap server if Samba4 can act as one? Thanks... -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Why not use Samba4 as LDAP?
On 2013-12-10 05:19, Burk Al wrote: Hi, I am going through documentation and doing test setups (many) for a while to be able to use Sogo's native outlook connection feature. My problem is not mainly for the setup or configuration but to figure out the best suitable underlying architecture. The documentation says Samba4 is required for native outlook support, if an ldap server or AD is in-place as a user directory the sync scripts are not provided and also says Samba4 can act as an ldap server. If I am starting from scratch, why would I bother with a separate ldap server, since Samba4 is sort of an ldap server and a requirement anyway. Right? I guess not. I have checked Sogo's ZEG and a separate ldap server is implemented. I have also took a quick look at Zenytal Server 3.3, which includes sogo and openchange in order to provide native outlook connection feature and they have also implemented a separate ldap server as well. Now I am wondering what could I have been missing? Why would I want to go with an additional ldap server if Samba4 can act as one? That's actually a good question, as Samba4 seems to discourage the use of dedicated LDAP servers ( https://wiki.samba.org/index.php/FAQ#Why_is_the_LDAP_backend_.28used_so_successfully_in_classic_Samba_domains.29_not_supported_with_the_AD_DC.3F ). Sogo seems to work fine with a pure Samba 4 AD setup ( http://www.foteviken.de/?p=1925 ). Thanks... -- Mit freundlichen Grüßen, / Best Regards, Sven Schwedas Systemadministrator TAO Beratungs- und Management GmbH | Lendplatz 45 | A - 8020 Graz Mail/XMPP: sven.schwe...@tao.at | +43 (0)680 301 7167 http://software.tao.at TAO Software befindet sich vom 23.12.2013 bis einschließlich 06.01.2014 auf Betriebsurlaub. Ab dem 07.01.2014 sind wir gerne wieder für Sie da. Bis dahin wünschen wir Ihnen ein frohes Fest, schöne Feiertage und einen guten Start ins Neue Jahr! Company holidays: 2013-12-23 to 2014-01-06 (inclusive). Merry everything signature.asc Description: OpenPGP digital signature
Re: [SOGo] Why not use Samba4 as LDAP?
Hello Am 2013-12-10 12:40, schrieb Sven Schwedas: On 2013-12-10 05:19, Burk Al wrote: Hi, I am going through documentation and doing test setups (many) for a while to be able to use Sogo's native outlook connection feature. My problem is not mainly for the setup or configuration but to figure out the best suitable underlying architecture. The documentation says Samba4 is required for native outlook support, if an ldap server or AD is in-place as a user directory the sync scripts are not provided and also says Samba4 can act as an ldap server. If I am starting from scratch, why would I bother with a separate ldap server, since Samba4 is sort of an ldap server and a requirement anyway. Right? I guess not. I have checked Sogo's ZEG and a separate ldap server is implemented. I have also took a quick look at Zenytal Server 3.3, which includes sogo and openchange in order to provide native outlook connection feature and they have also implemented a separate ldap server as well. Now I am wondering what could I have been missing? Why would I want to go with an additional ldap server if Samba4 can act as one? That's actually a good question, as Samba4 seems to discourage the use of dedicated LDAP servers ( https://wiki.samba.org/index.php/FAQ#Why_is_the_LDAP_backend_.28used_so_successfully_in_classic_Samba_domains.29_not_supported_with_the_AD_DC.3F ). Sogo seems to work fine with a pure Samba 4 AD setup ( http://www.foteviken.de/?p=1925 ). OpenLDAP was nessecary because of the change password functionality in SOGo. As SOGo can now change passwords in SAMBA/AD too, there is no need for an additional LDAP server anymore. Kind regards, Christian Mack -- Christian Mack Gruppe Informationsdienste Rechenzentrum Universität Konstanz -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Why not use Samba4 as LDAP?
On 13-12-09 11:19 PM, Burk Al wrote: Now I am wondering what could I have been missing? Why would I want to go with an additional ldap server if Samba4 can act as one? For normal use, using samba4 as the LDAP server for sogo should work just fine. There is however a limitation in openchange/sogo design: all calls to it are blocking, while the rest of samba is non-blocking. This causes issues when debugging samba/openchange/sogo, since one must run samba as a single process/thread (samba -i -M single). LDAP requests made from the SOGo backend will always block while calling the ldap server. However, since the process is running in a single thread and that thread is blocked, the LDAP server will never get the request. Hence the process will simply stall until a timeout is reached. If you run SOGo with the samba4 ldap backend, you won't be able to run gdb against it. This means that in case of a crash, it will be really hard to get a meaningful stack trace, so we won't be able to help out as much. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Why not use Samba4 as LDAP?
2013-12-10 14:59 keltezéssel, Christian Mack írta: Hello Am 2013-12-10 12:40, schrieb Sven Schwedas: On 2013-12-10 05:19, Burk Al wrote: Hi, I am going through documentation and doing test setups (many) for a while to be able to use Sogo's native outlook connection feature. My problem is not mainly for the setup or configuration but to figure out the best suitable underlying architecture. The documentation says Samba4 is required for native outlook support, if an ldap server or AD is in-place as a user directory the sync scripts are not provided and also says Samba4 can act as an ldap server. If I am starting from scratch, why would I bother with a separate ldap server, since Samba4 is sort of an ldap server and a requirement anyway. Right? I guess not. I have checked Sogo's ZEG and a separate ldap server is implemented. I have also took a quick look at Zenytal Server 3.3, which includes sogo and openchange in order to provide native outlook connection feature and they have also implemented a separate ldap server as well. Now I am wondering what could I have been missing? Why would I want to go with an additional ldap server if Samba4 can act as one? That's actually a good question, as Samba4 seems to discourage the use of dedicated LDAP servers ( https://wiki.samba.org/index.php/FAQ#Why_is_the_LDAP_backend_.28used_so_successfully_in_classic_Samba_domains.29_not_supported_with_the_AD_DC.3F ). Sogo seems to work fine with a pure Samba 4 AD setup ( http://www.foteviken.de/?p=1925 ). OpenLDAP was nessecary because of the change password functionality in SOGo. As SOGo can now change passwords in SAMBA/AD too, there is no need for an additional LDAP server anymore. Yes, since 2.1.0 it is not problem on Samba4 AD! :) -- users@sogo.nu https://inverse.ca/sogo/lists
