Zimbra + LDAP + Posix + Samba

[Greg]

Looks like this one: Bug 24861 - DomainAdmin login fails with posixaccount/samba zimlets enabled ?

[Greg]

Just fixed the bug (will be in 5.0.3) and fixed some errors in the HowTo for Zimbra+Samba integration.

[adewhurst]

Thank you very much for your help Greg, it's much appreciated!

[montyZdog]

I have a slightly different problem.
After upgrate directly from 4.5.5 to 5.0.2 everything is working but Admin interface is very slow to load when zimbra_posixaccounts and zimbra_samba zimlets are deployed.
I still CAN login as a Domain Admin user as well as a Zimbra admin user who does not have posix/samba account. But the picture is the same. When a browser is reloaded Admin interface can be accessed. When I log out and log back - the browser (Firefox) hungs with this message in the status line:
Loading script:/zimbraAdmin/res/zimbra_posixaccount.js?v=080130223433
If I then go to Advanced preferences and clear the cache - I am able to load the Admin interface again.
Since as I mentioned, I am able to login to Admin interface as Domain Admin, this is not exactly the case of the discovered bug.
I wonder, if the fix in 5.0.3 also address the above problem?

[montyZdog]

Originally Posted by Greg

Just fixed the bug (will be in 5.0.3) and fixed some errors in the HowTo for Zimbra+Samba integration.

Greg,
In my contributed paragraph on Configuring on RHEL5/CentOS5/Fedora7 using authconfig should there be changes in /etc/ldap.conf example?
I mean if binddn should be changed to "cn=config" for Zimbra 5.x ?

[montyZdog]

[Follow up]
The above mentioned problem with the Admin interface has gone after I read about Bug 24477 and removed 'sambaAccount'. I kept sambaSamAccount and posixAccount installed as per Wiki. Everything seemingly works and I can mange Samba accounts with Zimbra 5.0.2 GUI including creation of new ones (With 'sambaAccount' loaded I had the error featured in Bug 24477)
Question now, how do 'sambaAccount' and 'sambaSamAccount' relate? Is it OK if only the latter is installed?
The Wiki on Zimbra-Samba integration has no mention of 'sambaAccount'

[Greg]

Originally Posted by montyZdog

Greg,
In my contributed paragraph on Configuring on RHEL5/CentOS5/Fedora7 using authconfig should there be changes in /etc/ldap.conf example?
I mean if binddn should be changed to "cn=config" for Zimbra 5.x ?

Yes, binddn should be changed to "cn=config"

[Greg]

Originally Posted by montyZdog

[Follow up]
Question now, how do 'sambaAccount' and 'sambaSamAccount' relate? Is it OK if only the latter is installed?
The Wiki on Zimbra-Samba integration has no mention of 'sambaAccount'

sambaAccount and sambaSamAccount are both auxiliary classes for posixAccount. You should not be using both classes at the same time, because they conflict. sambaSamAccount was introduced in Samba 3 to replace sambaAccount. You can look into Samba release notes for more details about this, but the bottom line is use sambaSamAccount and do not use sambaAccount.

[montyZdog]

Originally Posted by Greg

the bottom line is use sambaSamAccount and do not use sambaAccount.

Thanks!
Though I've never specifically add 'sambaAccount' myself. When configuring samba integration in 4.5.5 I added 'sambaSamAccount'. Also,there are several posts in this topic
[SOLVED] Unable to add a new account. that mentioned the existence of both 'sambaAccount' and 'sambaSamAccount' after upgrade to 5.0.2.
I upgraded directly from "Samba-inegrated" 4.5.5 to 5.0.2. Then removed the old versions of extensions and installed new ones. Could it be that upgrade routine somehow adds 'sambaAccount' that later conflicts with 'sambaSamAccount'?

[Greg]

Originally Posted by montyZdog

Thanks!
Could it be that upgrade routine somehow adds 'sambaAccount' that later conflicts with 'sambaSamAccount'?

Hm.. I am not aware of any upgrade scripts that would add sambaAccount to zimbraAccountExtraObjectClass