#1821 Incorrect Samba objectclass causes LDAP corruption


I have a couple of test unix users in my LDAP
directory, and all works fine. When I attempt to add
samba support to the users with ldap-useradmin (LDAP
Users and Groups) by ticking the Samba login box and
then saving I get an I/O error message and my LDAP
server dies, corrupting the database.

"Failed to save user : Failed to modify user in LDAP
database : I/O Error"

This was because I forgot to change the Samba
objectclass name in the module options, but still, I
doubt this is the ideal way to handle a
misconfiguration error. Idelly all that is needed is a
simple check that the specified schema is availible on
the sever with appropriate action taken on the outcome.

Just for reference, I'm running an up to date Debian
Sarge system, but with the webmin modules from the
current Debian Sid (Webmin at 1.160-2). Accordingly,
Samba is at 3.0.7-2 and OpenLDAP is at 2.1.30-3.


  • Jamie Cameron

    Jamie Cameron - 2004-11-02
    • status: open --> closed
  • Jamie Cameron

    Jamie Cameron - 2004-11-02

    Logged In: YES

    All Webmin does when the Samba option is enabled is add the
    sambaAccount object class to the user. If this corrupts the
    entire LDAP database, it really looks like an LDAP server bug!


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks