Directory administrator
Directory administrator is a smart LDAP directory management tool. It can be used to manage UNIX and Samba user accounts and groups in a single sign-on setup, corporate address book information, host-based access control and advanced email routing. It's extremely easy to install and use, yet powerful at the same time.
| Tags | Systems Administration |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX Linux AIX BSD HP-UX Solaris |
| Implementation | C |
Recent releases
- 06 Jan 2005 09:51
Changes: The LDAPv3 connection code has been reworked, and now functions.
- 13 Jun 2003 02:05
Changes: In this version, a double free bug in the add secondary members window was fixed, enforcing of UID and group name uniqueness has been added to Directory administrator, in this version for the entire directory, when user UIDs change, all groups they are a member of are automatically updated, the dependency on the person object class was removed (OpenLDAP 2.1), a bug regarding anonymous profile connections was squashed, all connections now default to version 3 of LDAP protocol, but fall back gracefully, and some compile time errors for GCC 2.95 were fixed.
- 11 Jun 2003 00:07
Changes: A filter tool bar was added and keyboard navigation improvements were made. When users are deleted, all traces of them are now removed from every group. No primary groups can be deleted.
- 17 May 2003 12:57
Changes: Group handling was improved: DA now keeps group lists in sync automatically, whether you delete, add, or modify an user. Primary members are also added to the DN members list. Adding a user to a group is extremely easy now--there's a filter which will help a lot with large directories. Fixes were made for usability, user interface, and stability issues, as well as a few minor bugs.
- 10 Feb 2003 17:33
Changes: An extraneous bug was fixed that cropped up when creating an user. DA shouldn't segfault anymore as a result of that (although it may fail in creating the user). An off-by-one non-security bug was fixed that miscalculated the expiry date when checking the Expire this account on: checkbox in the user properties dialog. Other bugfixes were also made.
- All comments
Recent commentsRe: protocol version 3
> Hi
>
> I have been looking at LDAP for about
> 1day now and downloaded your client
> because it is the best. But I have one
> problem maybe it is because I don't know
> how to work it or something but how do I
> get your client to use protocol version
> 3.
>
> Thanx
> Jsdaav
>
> jsdaav@mweb.co.za
LDAPv3 support was not working previously. I submitted a patch that fixes this, yesterday.
protocol version 3
Hi
I have been looking at LDAP for about 1day now and downloaded your client because it is the best. But I have one problem maybe it is because I don't know how to work it or something but how do I get your client to use protocol version 3.
Thanx
Jsdaav
jsdaav@mweb.co.za
Re: poor security for directory credentials
> This program (at v1.5.1) stores your
> directory login credentials
> in a file with the default permissions
> of your umask, in my case
> 0664.
Hi there, xipmix. Sorry you got such a scare, but you
could have checked the permissions in the directory
(.directory_administrator). It's 700. So there's no
chance any user with access to your home directory
can access the passwords and settings file.
poor security for directory credentials
This program (at v1.5.1) stores your directory login credentials
in a file with the default permissions of your umask, in my case
0664.
This is not acceptable, on any multiuser machine. The program
should force restrictive permissions on this file, like 0600.
I can't think of a reason why you would want any other person
to have access to these credentials.
I won't be using this software until this is fixed.
In case it matters I was using the debian package,
http://download.cmeerw.net/debian/directory-administrator/binary-i386/directory-administrator_1.5.1-0cmeerw_i386.deb
Group Memberships
Greetings,
I have just downloaded the latest and greatest directory admin and it seems that the handling of groups has changed.
When I make a group a users primary group then an entry like this is added to that particular group;
member uid=bstewart,ou=Users,o=waterwerks
When I add a user as a secondary member of a group DA adds
member uid=bstewart,ou=Users,o=waterwers and
memberUID bstewart
Does anybody know why adding a users as a primary member of a group doesnt add the second line, but adding as a secondary users does ?
Thanks
Ben