User disappeared from Admin Account List

[andremta]

I tried once to configure Zimbra with SAMBA for my username (I'm also the admin) but things don't went in the manner as I expected so I quick gave up on this idea and tried to roll back the configuration.

Since then, my username has disappeared from the admin account list.

Another important information, with my username when I try to save any Preferences, I have this error:

invalid request: LDAP schema violation: [LDAP: error code 65 - unrecognized objectClass 'posixAccount']

Did I miss something while trying to roll back the configuration?


I'm using Zimbra v5.0.11 OSE

[ArcaneMagus]

Looks like your user account still has the posixAccount object class on it. To get it to re-appear in the lists you will need to remove the posix and samba object classes.

[andremta]

Originally Posted by ArcaneMagus

Looks like your user account still has the posixAccount object class on it. To get it to re-appear in the lists you will need to remove the posix and samba object classes.

Where do I have to remove those objects?

[ArcaneMagus]

The problem is in your LDAP account. All the standard disclaimers about how this could screw something up applies... (ie take a backup before trying this) but this worked on my server for a test account that I created. I have the Samba/POSIX LDAP extensions so the attributes that were on this users were the standard ones created.

First create the following file, modifying the dn: field to your user account.

dn: uid=asdf,ou=people,dc=domain,dc=com
changetype: modify
delete: sambaDomainName
-
delete: sambaAcctFlags
-
delete: sambaNTPassword
-
delete: sambaSID
-
delete: gidNumber
-
delete: uidNumber
-
delete: homeDirectory
-
delete: loginShell
-
delete: objectClass
objectClass: posixAccount
objectClass: sambaSamAccount
-

Then once you have created that file (I created it as /tmp/asdf.ldif) run the following command:

ldapmodify -x -H ldapi:/// -D uid=zimbra,cn=admins,cn=zimbra -w `zmlocalconfig -s zimbra_ldap_password | cut -f3 -d" "` -f /tmp/asdf.ldif

If you have extra attributes that are causing an error in that command add them to the .ldif file.

What this does is delete all the attributes that are specific to the sambaSamAccount and the posixAccount object classes, and then removes those object classes from the account.

[andremta]

Originally Posted by ArcaneMagus

The problem is in your LDAP account. All the standard disclaimers about how this could screw something up applies... (ie take a backup before trying this) but this worked on my server for a test account that I created. I have the Samba/POSIX LDAP extensions so the attributes that were on this users were the standard ones created.

First create the following file, modifying the dn: field to your user account.

dn: uid=asdf,ou=people,dc=domain,dc=com
changetype: modify
delete: sambaDomainName
-
delete: sambaAcctFlags
-
delete: sambaNTPassword
-
delete: sambaSID
-
delete: gidNumber
-
delete: uidNumber
-
delete: homeDirectory
-
delete: loginShell
-
delete: objectClass
objectClass: posixAccount
objectClass: sambaSamAccount
-

Then once you have created that file (I created it as /tmp/asdf.ldif) run the following command:

ldapmodify -x -H ldapi:/// -D uid=zimbra,cn=admins,cn=zimbra -w `zmlocalconfig -s zimbra_ldap_password | cut -f3 -d" "` -f /tmp/asdf.ldif

If you have extra attributes that are causing an error in that command add them to the .ldif file.

What this does is delete all the attributes that are specific to the sambaSamAccount and the posixAccount object classes, and then removes those object classes from the account.

Arcane,

I'm having this problem:

dn: uid=myuser,ou=people,dc=doain,dc=com
changetype: modify
delete: objectClass
objectClass: posixAccount
objectClass: sambaSamAccount
-

zimbra@intranet:/tmp$ ldapmodify -x -H ldap://192.168.1.2 -D uid=zimbra,cn=admins,cn=zimbra -w `zmlocalconfig -s zimbra_ldap_password | cut -f3 -d" "` -f /tmp/zimbra.ldif
modifying entry "uid=myuser,ou=people,dc=domain,dc=com"
ldapmodify: Invalid syntax (21)
additional info: objectClass: value #0 invalid per syntax
zimbra@intranet:/tmp$

What this could be?

[ArcaneMagus]

Searching google it seems that is a common problem when you have a space after the objectClass name, or the wrong endlines on the file.