LDAP Tools - Where are they? 350
fixe asks: "I have spent the last few months up to my eyeballs in LDAP. While I am still hopeful of what LDAP can bring to the table I am admittedly disappointed in the tools, support and documentation surrounding the standard. I have been successful at creating and populating an LDAP directory and even authenticating against it, however I cannot find decent replacements for useradd, userdel, usermod, passwd, etc. Nor have I found any decent LDAP editors or browsers (preferably console or web-based). I am hoping that the Slashdot crowd might be able to shed some light on the subject. Are there any LDAP veterans out there who can reccommend any tools? What is the best way to maintain system account synchronization with an LDAP directory? Or perhaps, is there a more attractive alternative to LDAP?"
Check out Microsoft's tools (Score:3, Informative)
Also, check out gq , which is a pretty nice GTK+ based LDAP client. It's still very barebone, but it's better than the commandline tools for a lot of tasks.
Re:Check out Microsoft's tools (Score:5, Informative)
AFAIK, it supports LDAPv2, LDAPv3 and Active Directory. It supports most all SASL mechanisms, even NTLM when necessary.
I know what you mean. (Score:5, Informative)
http://www-unix.mcs.anl.gov/~gawor/ldap/
It is the best thing out there as far as I can tell.
Rick
I'm a river of knowledge to my people (Score:5, Informative)
GQ is also worth a look (Score:3, Informative)
in that directory'
It comes as Red Hat's standard LDAP admin tool. Get it here [biot.com]. Its not as good be, but neither is directory administrator the last time I looked.
Re:I know what you mean. (Score:2)
There have been some fixes to those scripts that haven't made it to the downloadable version yet - but they were adequate for my needs at the time (a couple of years ago). Maybe a good start for someone wanting to do their own? I dunno - I was in a hurry...
my preferred LDAP browser (Score:5, Informative)
You would think that wrapping a gtk+ interface around ldapsearch would be a straightforward and no-brainer proposition, but you would apparently be wrong.
Re:my preferred LDAP browser (Score:3, Informative)
For a command-line add/modify/delete utility, here's one I created:
http://pushan.integritysi.com/down/ldapuser [integritysi.com]
Re:my preferred LDAP browser (Score:2)
Only the last one had some issues, but unfortunately I wasn't able to help the kind Softerra people (who were very responsive during the beta-test) out with it because I've changed jobs since.
For those wanting to administrate an LDAP server (eg: adding/removing/editting entries), I would definately advise LDAPAdministrator
Windos tools (Score:3, Informative)
IBM LDAP Client (Score:4, Informative)
LDAP Admin Tools (Score:2, Interesting)
http://freshmeat.net/projects/sldapa/
http://freshmeat.net/projects/directoryadmin/
JAVA LDAP BROWSER (Score:2, Redundant)
To get it:
Go to google, search for "ldap browser" and click "I'm feeling lucky".
Enjoy.
My Favorite tools (Score:4, Informative)
Also, I REALLY like the java LDAP Browser for GUI use (available from http://www.iit.edu/~gawojar/ldap)
As far as account creation tools, there's some nice trends among the big user provisioning corporate grade systems (i.e. Access360) to manage accounts in LDAP.
I'd stay away from Active Directory since it doesn't follow all of the standards. eDirectory's only big annoyance is that it's LDAP is actually a mapping on top of their old stuff, so sometimes that adds complexity. But for a long time they had the only multi-mastered replication setup. iPlanent now has that and MS/AD kinda does (but they have crappy granularity on their objects in case of collisions).
libnss-ldap (Score:4, Offtopic)
Anything but OpenLDAP (Score:5, Informative)
So, whatever you do, AVOID OpenLDAP.
Re:Anything but OpenLDAP (Score:2)
Are there any other free (in either sense) LDAP servers, though? All the others appear to be closed and/or $$$.
Re:Anything but OpenLDAP (Score:3, Interesting)
OpenLDAP dies a lot over here too. Replication works quite well for us, the only "problem" ist that slurd opens lots of processes for every replication target - our main ldap-machine is running about 750 processes at all times.
Don't even dare to try any 2.XX version of openldap - they have a lot of features you probably don't need and are even more buggy.
Re:Anything but OpenLDAP (Score:4, Insightful)
It all works fine on someone's home machine, because it's never under any load. Try to put it into a moderate production environment, though, and it all falls down go boom.
I used to hear similar comments about open source NIS implementations 3-4 years back.
So you either start load testing it yourself, understand why it's broken and fix it. Or go with a commercial product that has already been through this process.
Re:Anything but OpenLDAP (Score:2)
A Samba server that I installed for a client has an uptime of around 500 days - it has never crashed. The reason I installed Samba: the NT server it replaced would crash about once a week.
It looks like the open source Samba is better than the comercial NT.
There are other examples:
OpenSSH has less secutity holes than SSH
IPF is better than XP's 'firewall'
LaTex is better than.. well anything
MIT Kerberos is better than MS Kerberos
So your blanket statment that comercial is nesessarly better than OpenSource is false. Enjoy.
Re:Anything but OpenLDAP (Score:3, Insightful)
No I'm saying that any time you post a query about most open source projects not working for you because of load issues, the response is "It works fine on my little home network."
Listen, load and stress testing an application takes a fair amount of resources. It takes money to buy the test hardware and execute tests and such. This isn't something most people can do on their little home networks, so it takes corporate investment to make it happen.
How many people do you know who have a dozen servers and 200 desktops sitting in a room just waiting around for someone to setup and run some tests?
Companies like Compaq, IBM, Microsoft, and so forth have these resources. If Compaq and IBM view OpenLDAP(or whatever) to be critical, perhaps they will make their testing labs available to the open source developers.
Otherwise you are relying upon testing in production, which is not the way to win friends.
Re:Anything but OpenLDAP (Score:2, Informative)
We populate the directories live, but some complexities with our own record keeping requires a bulk reload weekly -- so the daemons are restarted at least once a week.
Re:Anything but OpenLDAP (Score:2)
Re:Anything but OpenLDAP (Score:5, Informative)
Re:Anything but OpenLDAP (Score:2)
GTK based LDAP browser (Score:2, Interesting)
Java based browser/editor (Score:2, Informative)
http://www.iit.edu/~gawojar/ldap/index.html
Re:Java based browser/editor (Score:3, Insightful)
What about "Directory Administrator"? (Score:4, Informative)
My advice is to create two user hierarchies: one for administrative non-human accounts (e. g. root, mail, www) and one for real users. Same thing for groups. This way you can manage your real-user accounts with some kind of GUI frontend and even re-use the objects in an addressbook like Evolution Contacts without risking a security hole.
This has been a huge problem for us as well (Score:5, Informative)
Probably the most frustrating part is if you go on google and look for help, you see people mentioning that this works, but never any specifics. I assume you are just using pam_ldap to grab a password crypt from an LDAP server (which is a secure as giving everyone read permissions on your shadow file).
I think the best solution is to use an LDAP server to host all the user information that is normally in
Re:This has been a huge problem for us as well (Score:2, Informative)
I've integrated myself several Windows, Linux and Solaris boxes under iPlanet Directory Server (which by the way, is free up to 200.000 directory entries).
The problem arise when you try to use Microsoft propietary LDAP (aka Active Directory). Just throw Active Direcotry away. Download for free Solaris 8 for Intel, download the latest LDAP Directory Server for Solaris Intel from iPlanet home page, and you will get plenty of docs from within iPlanet's site, and even Sun site. You can even call your Sun SE and get him to find all the documentation needed to integrate a Windows, Linux Solaris enviroment.
Realllllyyyyy ease!!
Re:This has been a huge problem for us as well (Score:3, Interesting)
Failing that AD/LDAP is pretty easy to script using ADSI interfaces.
I've never done what you are looking at, but it doesn't seem like it should be that difficult.
Re:This has been a huge problem for us as well (Score:5, Funny)
You have a very promising career in technical management.
Re:This has been a huge problem for us as well (Score:3, Interesting)
Re:This has been a huge problem for us as well (Score:2, Interesting)
Some things you can use (Score:2, Informative)
If you want an all-in-one solution (Server & Gui to populate server), try the iPlanet Directory Server which is kind of free to use (downloadable at netscape.com) and has a really nice interface.
Another nice (non-free) thing is an LDAP-API for Visual Basic from SnarkSoft [snark-soft.com] which allows you to quickly write applications using data from your LDAP server. I know this isn't really a LDAP-solution, but it allows you to easily develop LDAP applications.
linux/unix LDAP user tools (Score:4, Informative)
[open-it.org]
directory_administrator which is a GNOME LDAP user admin tool (slick enough for use by a frontline helpdesk).
there are other LDAP GUI's, KDE has one. search freshmeat.
gq [biot.com] a general purpose LDAP GUI tool. quite slick, comes with RH7.x.
Also, note that with RH7, the 'passwd' tool uses pam and will hence automatically work with LDAP authentication. (presuming your LDAP server is configured correctly for write access).
finally, you'll probaby want to develop your own scripts with template LDIF's for things like useradd, or find someone who's already done so. (i noticed there's a post on this thread providing a link to exactly that.) Note that for scripting, PADL's [padl.com] migration scripts are very informative. These are included with the OpenLDAP distribution.
widely implemented at my university (Score:2)
You're not looking hard enough (Score:3, Interesting)
If you have paid careful attention, you will notice that LDAP support has crept into hundreds and hundreds (of not thousands) of applications over the last year. The API's for doing LDAP programming yourself are also extremely well developed imho. You have options for C, PERL, C++, Python and a slew of other programming languages. Search Freshmeat or Sourceforge for LDAP and see what you come up with, I think you'll be surprised.
I don't think LDAP is dead, I think it's one of those protocols like TCP that just sneaks up on you with it's usefulness
LDAP is quite useful where I am (Score:4, Informative)
If you're seeking some bonafide support options, you might confer with openldap.org, or better yet iPlanet's Directory Server. The latter would cost some money, but it is an option.
The ultimate tool. (Score:4, Interesting)
That's right you can do all this and a whole lot more, using Novell Netware. Even if you don't use Netware, eDirectory (included in Netware or sold separately) allows a lot of these functions from within the Java based Console One. It runs on almost any platform, available today. It even has additional modules that allow things like single signon and more. That's right, all the advantages of
Even if it isn't free, for enterprise use, it is down right cheap!
Re:The ultimate tool. (Score:2)
Also, don't forget the metadirectory approach as a valid one for trying to manage LDAP and other directories: Ganymede is the only open source project in this space that's much good, and it's starting to look fairly capable.
Still, you get what you pay for: If you're making directory services a core part of your IT strategy (not a bad idea, but realize there are other approaches now, with Java, XML, etc.), it's worth buying the real stuff from Novell or iPlanet. Unfortunately, there's been little open source work in this area: if the open source products work at all (many don't), they don't scale and lack important features.
That's too bad, because tying together things like MSWallet,
LDAP Admin Help (Score:5, Informative)
Let me rephrase that: the protocol is mature and useful, and the servers by and large are mature and useful, but the support tools stink, as a general rule. Since it sounds like you are mostly concerned with user administration, I will stick to just that, and let other people mention tools they've found useful.
If you are using Solaris, AIX or Macintosh, using LDAP for accounts is pretty trivial, since the OS supports it directly - you'll need to have the POSIX user schema loaded, and point the OS's naming service to LDAP instead of its local database. Win2K/XP kind of force you to use Active Directory, so you are also taken care of there. In all of these cases, accounts other than the system superuser will be in LDAP, and so therefore synchronization is not a problem.
useradd, userdel, usermod and passwd are all replaced by ldapmodify, or you can use the tools included with some servers (the iPlanet console being a good example of how to do this right). Right now, there doesn't seem to be any substitute for thoroughly learning ldapsearch and ldapmodify, Perl and Net::LDAP. You can use ldapsearch and ldapmodify for quick actions (adding, modifying or deleting a single user, or changing a password) and Perl and Net::LDAP for more complex operations (or for putting together a CGI for common functions like changing a user's password).
I find I end up writing built-to-purpose Perl tools just about everywhere I go. In some cases, this is because of differences in admin policy at different sites, or differences in schema. In others, the issue is more contractual (whomever is paying me gets ownership of the code I write, so I have to rewrite from a clean sheet at the next site).
The good news is, it is fairly quick and painless to write replacements for useradd, usermod, userdel and passwd which can be run from the command line or as a CGI, and you only have to write them once for your site, if you write them well in the first place.
-jeff
From a purely simplistic view, LDAP is pointless (Score:2, Interesting)
all kinds of great contact / location / description information, but how is it used in reality? It is used as a really difficult to use properties file. Judging the way most people use LDAP that I've seen, they would have been better off with a sql database. At least with SQL the queries are readable. (o=, c=, wtf= is a pain).
The way I feel about it is that the LDAP 'problem' does exist and is solvable, but the right protocol/implementation does not yet exist. Until something much more friendly and useful comes along, I am firmly off the LDAP bandwagon.
So if you're looking for a good tool to solve your LDAP problems, I suggest Oracle, PostgreSQL or MySQL.
Re:From a purely simplistic view, LDAP is pointles (Score:3, Informative)
Here is some information comparing LDAP and SQL from the OpenLDAP FAQ:
http://www.openldap.org/faq/data/cache/378.html
And here is some from an old usenet post. It's specifically talking about why Netscape's LDAP server uses it's own database instead of a RDBMS, but it has lots of good information about how directory services and RDBMS's differ and why one does not make a good substitute for the other.
http://groups.google.com/groups?q=ldap+comparis
LDAP and its place today (Score:2)
Though not heavily deployed in the enterprise, ESPECIALLY *nix, basically due to the very issues you mention (few admin tools, high complexity), it is heavily used on the web and in Microsoft-centric environments. Active Directory almost follows the LDAPv3 protocols (two non-standard areas are both related to schema implementation. The variations are well documented and do not drastically effect applications)
My admin tool of choice? Sad to say, it is the AD administrator. Second admin tool of choice? Microsoft Site Server 3.0, Commerce Edition's Membership Directory Manager MMC snap-in. Both are Microsoft Management Console snap-ins, but if you can get around that they work alright. The MSS3CE version is even fully LDAPv3 compliant, so you can use it with other directories, too. It also comes with a web interface you can use.
As far as non-MS tools? Haven't seen a one worth it's salt, though a couple of my co-workers recommend talking to the NetIQ folks if that's your bend...
Just saw this on a mailing list: (Score:4, Informative)
Carillon Information Security Inc. would like to announce the release of
KDirAdm version 0.1
K DIRectory ADMinistrator is a tool for use by Directory Administrators to
manage their LDAP based directory. Using the K Desktop Environment (KDE) and
OpenLDAP toolsets, this application currently has all of the basic
functionality required to browse, add, and delete directory entries. As this
is an initial BETA release, the capability to modify existing entries, as
well as the ability to handle binary directory objects is currently missing.
This is planned for the next release, along with improved password entry
handling and possibly LDAP over SSL support.
KDirAdm is open source software released under the GNU Public License. As
such we encourage anyone to help us in the development of this software.
Specific jobs that need doing at the moment are improving the documentation,
the artwork, and of course, any LDAP wizards that want to help out will be
greatly appreciated.
The homepage for KDirAdm is at:
http://www.carillonis.com/kdiradm
where both source and Debian packages may be obtained.
Comments, suggestions, wishlist items and patches may be sent to
ppatterson@carillonis.com
So, it's "pre-beta" but has that ever stopped a true free software geek before?
Novell has some pretty cool LDAP tools! (Score:2, Informative)
ConsoleOne is a graphical, cross platform GUI tool that allows you to do pretty much every thing. Add, Delete, Create, Modify, Search, Extend the schema, etc.
There's also the ICE (Import, Convert, Export) tool which allows you to import, convert and export data from LDIF or other LDAP servers. ICE is available in a GUI and command line version.
eDirectory is also managable through a browser, and if you use their DirXML product you can basically take any data from any system and expose it through LDAP.
Novell's eDirectory is redistributable for developers. If you do development work, check all their goodies at their development site [novell.com]. You'll find LDAP class libraries, tools etc.
The evaluation copy of eDirectory can be found here [novell.com] and includes the tools mentioned.
LDAP, Tools, Servers et al (Score:5, Informative)
from my own experience I can tell you that:
1 - The best available tools are definitely the command-line that come with most servers.
2 - OpenLDAP sucks big time in large scale environments. It's replication is anything but reliable
3 - GQ is a very, very nice browser for LDAP. But I wouldn't use it for administration.
4 - You can assemble a whole range of ISP services (mail, ftp, http, whatever) based on an LDAP tree. Even if you can't find a _insert favorite daemon here_ supporting LDAP, you can always use...
5 - PAM/NSS LDAP. It just rocks. If you configure it properly, anything using PAM/NSS will use/update your tree accordingly. This includes unix tools like "passwd", "useradd", or "finger", or services like QPopper and OpenSSH.
6 - The best way to automate some processes is to create our own tools. Net::LDAP is very easy to use, and does anything you can think of (in terms of LDAP ops)
Dunno what you've got, but here's what RIT has... (Score:2)
A few tools (Score:4, Informative)
Object Identifiers
What about user tools? (Score:2)
There's not that many good user management tools for LDAP. I don't feel like typing it in on raw mode with GQ, when a lot of it is duplicate information (to make sure it gets caught with the different schema names).
LDAP tools? Open Source tools are here! (Score:5, Informative)
As for management, we now host Directory Administrator,a great GTK front end to user management, I have also created a simply useradd program for creating users in ldap (its called addluser).
We are currently working on a new release of Directory Administrator with a new backend which will allow CLI, GUI, and Web clients to be built on it. Further, if you love WebObjects, Apple just released 5.1, which has a JNDI adaptor, allowing quick Web Apps to be built against LDAP directory servers using Java.
Is the documentation not up to snuff at Open-IT, then help out! We have some basic howtos, and I package pam_ldap, nss_ldap, openldap, and other great things to get you going.
Back to work...
Re:LDAP tools? Open Source tools are here! (Score:2)
Ganymede, an LDAP manager / alternative (Score:5, Informative)
Well, I'll post a pointer to Ganymede [utexas.edu], which is not specifically for LDAP, but which could probably be useful in a lot of environments.
Ganymede is at once simpler than LDAP, in that it doesn't support the kind of hierarchical objects that LDAP and x.500 support, and in that it doesn't actually speak LDAP, and more complex, in that it has a sophisticated transactions model and can handle complex concurrent operations while maintaining namespace and referential integrity.
Ganymede is useful if you want to have a smallish (less than 50,000 users, say) 'flat' directory, but for which you want to allow detailed permisison delegation and fine-grained concurrency. If you have a very large NIS domain and you want to allow scores of users and admins to be changing their passwords and account information concurrently, Ganymede will work wonders for you.
We actually use Ganymede for just about everything here, up to and including our DNS, although we don't have our DNS support code 'productized' yet. We do master our LDAP directory from Ganymede data, in order to support applications which can use an LDAP server for an address book (such as Outlook and Netscape Messenger). If you were to combine Ganymede with something like Thomas Reith's ldapdiff [rhoen.de] utility, you could combine Ganymede's sophisticated administration services with LDAP for distribution.
Fun with LDAP (Score:3, Interesting)
If you are using LDAP as your addressbook, ldap-abook [freshmeat.net] is a nice interface to add/delete/modify entries. Most email clients are LDAP-aware these days and it's convenient to be able to share an address book between my personal and work email accounts.
I've had to roll my own to do system accounts, however. Make ldapmodify your new best friend, or write an interface of your own - there is a lot of support for Perl or PHP LDAP functions out there. Server-side, I've used OpenLDAP [openldap.org] and iPlanet's Directory Server [iplanet.com], and I prefer iPlanet. iPlanet has a free non-commercial license option, is significantly faster than OpenLDAP, and has hooks to synchronize with an NT or Active Directory domain so you could do all the user administration in Windows and they would propagate over to your LDAP server.
Other fun things you can do with LDAP are:
Handle Unix authentication through pam_ldap [padl.com]
Hook into NIS with the NIS/LDAP gateway [padl.com]
Authenticate through apache with mod_auth_ldap [nona.net] or auth_ldap [rudedog.org] or Netegrity [netegrity.com]
Centralize your smtp routing data in LDAP for sendmail
Good luck.
iPlanet Directory Resource Kit (Score:2)
-jeff
Webmin's LDAP plugin... (Score:3, Interesting)
Links: Webmin & Freshmeat page for LDAP module (LDAP module site is in French but easy to grok);
http://freshmeat.net/projects/ldap_module
Oracle does LDAP too (Score:2)
DSML and LDAP (Score:2)
It's not graphical, though
Find it here [dsmltools.org].
Gerv
One word: perldap (Score:2)
JDBC driver for LDAP (Score:2, Interesting)
OpenLDAP utils vs Net::LDAP (Score:2)
Also if you're running iPlanet/Netscape's directory server grab their resource kit, the ilash util which can do a lot of things, has a really nice feature in that you can drop an entry into vi and edit it. ud or whatever it's called in the OpenLDAP utils can sort of do that, but only for certain hardcoded attributes, and not the ones you're likely to need either.
Isn't Active Directory an LDAP implementation? (Score:3, Informative)
Slap me with a strongly worded post if I am incorrect, but isn't Active Directory an LDAP implementation?
Re:Isn't Active Directory an LDAP implementation? (Score:4, Informative)
To their credit, the Microsoft ADSI LDAP implementation is remarkably standards-compliant. I developed an app which authenticated users against OpenLDAP, and extended it to support ADSI as well with minimal effort (mostly involving generalization of assumptions about directory layout, rather than interface changes per se).
*sigh* (Score:3, Insightful)
1) If the public protocol is leaky, why not develop their own, totally different & competing protocol?
2) If they did care about the public domain issues and improvement, why not submit their improvements to the standards body to have their "improvements" included?
3) Failing or separate from this, why not license out their "improvements" to other software vendors? They would still make money, right?
I think the truth is that while it is possible that MS may have made a few small improvements (doubtful, but possible), their real goal is to ensnare new customers and to dig existing ones even deeper. If you still disagree, I would appreciate hearing any lucid arguments.
Re:Perhaps you've never done real business? (Score:2)
Would "gaining a business advantage first" do for a reason? Patent the improvements, refuse the license until you've gained a dominant market share and then release the innovation to the others. That's how business is done.
Microsoft has had a dominant business share for as long as I can remember. Furthermore, let me know when they license out Kerberos, Active Directory, ActiveX, ASP, DirectX, their Java extensions,
Re:Isn't Active Directory an LDAP implementation? (Score:3, Informative)
Re:Isn't Active Directory an LDAP implementation? (Score:2, Informative)
Its actually quite sane - and the problems we have had in developing with it have not be AD, its been the unix client tools making assumptions about a functioning DNS (hint: it doesn't exist on MS networks).
But with a few config file tweaks its perfectly practical to kinit to your AD KDC and use that for a secure authenticaion! (In the end Tridge rewrote our own mini implemenation of the required peices to work around the buggy SASL libs).
Andrew Bartlett,
Samba Team
Re:Isn't Active Directory an LDAP implementation? (Score:2)
Re:Isn't Active Directory an LDAP implementation? (Score:2)
Active Directory (Score:3, Interesting)
FWIW, Novell's NDS has been the only enterprise-class directory service since the mid-90's and AD is a play into this arena.
Of course, this is all moot since this is Slashdot and of course you aren't interested in technology from the Dark Empire (tm).
Re:Active Directory (Score:2)
Nope. iPlanet was there before AD (as Netscape) and is far ahead of AD in stability and scalability, as well as performance. I have not used NDS enough to comment intelligently about it. AD is LDAP, but in a quite broken way - much as Win2K supports DNS and DHCP, but in broken ways.
-jeff
Re:Active Directory (Score:3, Interesting)
Re:Active Directory (Score:2, Informative)
OT: Troll?! (Score:3, Offtopic)
-
Not a big industry player? (Score:3, Informative)
Re:Not a big industry player? (Score:3, Informative)
Another eDirectory user (Score:2, Interesting)
Re:Another eDirectory user (Score:2, Interesting)
With some imagination as well as use of eDirectory (which has been demonstrated publicly to scale to 1 billion users, and in-house at Novell to 3 billion) AOL/Time-Warner, or perhaps the Liberty Alliance, could provide a credible alternative to Microsoft/.NET/Passport.
Re:Directories are dead in the water (Score:3, Insightful)
XML is a file format (or metaformat), not a directory service like LDAP. The two technologies are orthogonal.
>its hard to make an argument of listing >another protocol on an isolated port to provide a >solitary service
<sarcasm> Yeah that's a great idea! Let's run everything over port 80! </sarcasm>
>There also doesn't appear to be much corporate interest - Microsoft has moved its mindshare >strategies to web services, leaving the only big backer of LDAP being Novell - not really a key >industry player at this point.
Hello?? Active Directory is LDAP based. Admittedly it's LDAP with the usual "embrace and extend" twists like proprietary Kerberos extensions and slightly non-standard schemas, but LDAP none the less.
Re:Directories are dead in the water (Score:2)
Thinking of LDAP as a storage system is the path to utter confusion. LDAP is an interface spec, more like http than like a web server. Any underlying system can support LDAP queries or http connections if it provides the correct interface behavior.
Re:Directories are dead in the water (Score:2)
They are related via DSML [dsml.org], and there's an open source suite of software that I wrote for working with directory information as XML here [dsmltools.org].
Gerv
Re:Directories are dead in the water (Score:2)
Exactly. The links you've included (looks like good stuff by the way), definately show how LDAP and XML can be used well together.
They are mutually independant technologies. They can be used together to complement one another, but to talk about replacing XML with LDAP or LDAP with XML (as the previous poster did) is just plain silly.
Re:Directories are dead in the water (Score:5, Informative)
And to answer the original question, eDirectory is the new name for Novell's NDS, a mature yet still evolving directory service that is fully LDAPv3 compliant. As it has been available for so long, there are MANY third-party tools and utilities available to manage it (such as Bindview or JRBUtils) in addition to Novell's own tools and utilities. Novell's eDirectory management utilities include import/export tools built in to ConsoleOne (an admittedly heavyweight Java-based management console) as well as BulkLoad, a command-line LDAP utility that uses LDIF files for command input. These utilities permit import/export of userids in LDIF format, as well as the migration of data between LDAP servers.
eDirectory is fully cross-platform, currently running on Netware, NT, 2000, Linux, Solaris, and Tru64 UNIX. It's been demonstrated at tradeshows with databases of up to one BILLION user accounts. Features of the latest version, 8.6, include persistent searches, dynamic groups, and live backup. The next release is expected to include UDDI, SOAP, and DSML 2.0 support.
Novell is practically giving eDirectory away at a list price of $2/user or less. They are actually giving it away for VARs and developers that wish to bundle eDirectory as the dedicated directory for their applications.
Oh, and if you wish to stay with open source options, look on Freshmeat.net for OpenLDAP - it includes a set of client utilities that should fit at least some of your requirements. Freshmeat should also have other LDAP clients, including browsers.
Re:There's NDS DAMN STRAIGHT! (Score:2)
YEs, goto Novell for the best directory, and the best LDAP software available.
You can use Novell's eGuide as a good user admin utility VIA ldap. I've never tried it with a generic LDAP directory, but it should work well.
IMHO, if you're going to do anything that requires a large directory, look at NDS. You'll get your basic LDAP services and a lot more, including replication.
Move up to a Novell Netware 6 server, and get load balancing / automatic failover with it!
Ever play a video file off your server, then down the server, and have the video pick up where it left off?
It just fucking rocks.
Novell's been "going out of business" for years... (Score:4, Informative)
The fact is there's a niche between small business (Microsoft products) and Fortune 100 (*Nix) where Novell's products reside quite comfortably.
And eDirectory is a full-featured LDAP implementation in its own right. Not to mention the free version [novell.com] for Linux! (Registration required).
Hey, whad'ya know, I see that
Here it is again in plain text for your cut'n'pasting pleasure:
https://download.novell.com/ICSLogin/?"http://d
Re:Uhh.... what's LDAP? (Score:2, Informative)
Acronym lookup dictionay for your reference:
http://www.ucc.ie/info/net/acronyms/acro.html
Re:Uhh.... what's LDAP? (Score:5, Informative)
LDAP was originally intended to be a more flexible and less resource intensive implementation of Directories (phone books are a good example but not the only one) a'la the older X.500 protocol.
LDAP has been embraced by alot of companies like Microsoft and Sun (my employer) as a core server technology to form the "glue" between distributed services.
One of the most common uses is to maintain remote password authentication databases. Similar in concept to RADIUS or NIS, but in a more standard implementation without all of the overhead.
For instance, Sun is moving it's internal network to LDAP authentication (originally it was unconnected, later they used NIS, both older systems are still in use at Sun right now). It allows an employee to use the same password for many different resources on the internal network while having a single place to update that password.
Re:Uhh.... what's LDAP? (Score:2)
Sure, Novell would have the tech to do it, but hell, this is the IT industry, which isnt about technology. It's about Microsoft taxing you for 30% of your income for the rest of your life. Nothing else.
Re:Uhh.... what's LDAP? (Score:2, Informative)
Lightweight Directory Access Protocol (v3)
This protocol is specifically targeted at management applications and browser applications that provide read/write interactive access to directories.
Re:Uhh.... what's LDAP? (Score:2)
For example, to represent the fact that I work for a company (let's call them Foo Inc) in the UK, you could write the following:
c=UK,ou=Foo Inc,cn=Tim Campbell
That identifies the object "Tim Campbell" in the organisational unit "Foo Inc" in the country "UK" (Sorry for any inaccuracaies and the general crapness of the example, it's been a long time since I messed with any LDAP stuff)
The only thing that I've used that uses LDAP is SiteServer, which uses it for the Personalisation and Membership service (which is why it's been such a long time
Cheers,
Tim
Re:ever hear of Freshmeat? (Score:2, Insightful)
Re:Life beyond LDAP (Score:4, Interesting)
Re:Why use LDAP? (Score:2)
I'm sure it's really good if you're trying to manage 50,000 users and a masochistic enough to like constantly editing ldif files but otherwise steer clear.
Re:Why use LDAP? (Score:3, Insightful)
NIS+ is a truly elegant architecture, in many ways, what AD should have been. It's far superior to AD, LDAP, or any other X.500-derived directory - that ISO/OSI brain damage is just too deep to let X.500's ilk be easily used in the real world.
Unfortuantely, Sun really botched its attempt to get NIS+ accepted, for several very good reasons:
1) Although the directory itself was incredibly impressive, and worked very well, there were NO administrative tools usable by mere mortals. I was a "Network Ambassador" at Sun at the time NIS+ was attempting to make inroads, and I can tell you that even amongst that elite group, not 1 in 50 was capable of setting up and properly administering NIS+ in a configuration suitable for enterprise use. Some things were just impossible, like recovering from a lost root key: You just had to rebuild everything from scratch. Secure, but hardly practical. This inordiante complexity may well be why there's still no Linux NIS+ server (besides the fact that one would be pointless now...)
2) There was no good migration plan from NIS to NIS+, and no way to keep the two in sync: it was pretty much an all-or-nothing scenario, at least for the Unix boxes. Not surprisingly, lacking Microsoft's arm-twisting ability, all but a handful of Sun's customers chose to pass NIS+ by, no matter how good it was.
3) Sun tried hard, but didn't make adopting NIS+ sweet enough for IBM and HP, who at one time had "committed" to putting NIS+ into their Unix OSes. Unfortunately, the combination of NIS+ being perceived as "Sun's" and its underwhelming adoption even solid Sun accounts (due to reason #1 above) led to its not being considered a serious contender.
4) If you really know what you're doing, it's possible to build a hierarchical multi-domain name/directory service using NIS, although I only know of one company (a Fortune 20 former employer) that's ever actually put this in production enterprise-wide. All the capabilities are there, it's just that very few people bother to figure out how NIS really works. We eventually wound up replacing regular NIS with a security-enhanced superset NIS (and appropriately modified utilities) of our own design, where all appropriate changes at a higher level filtered down to the lower domains, and each domain only had to administer its own portion of the namespace.
Sad, but I'd say NIS+ is pretty much completely irrelevant now.
Microsoft and AD have won this battle so far, but it may once again be the unlikely knight Samba that will save the day and turn the tide. We'll see.
P.S.: Side note to comment 1 above: This is just one in a long line of times Sun has developed extremely impressive core architectures and failed in the marketplace. (NIS+, SunNet Manager, Jini, Jiro, and even Java itself, to some degree...) The fallacious assumption is that the elegant core is all that's required, and that dealing with pesky details like administration, management, or writing apps that take advantage of the elegant plumbing can be left as an excercise for the customer, not something worthy of Sun's time and attention. When will they learn?!
The Secret OpenLDAP Speed Boost (Score:3, Informative)
There is a poorly documented (gee, surprise surprise) option to add indexes (at least for the ldbm backend). Try putting
index cn,gn,sn,uid,objectclass,o,ou pres,eq,sub
in your database definition in SlapD. Note that you will need to rebuild the DB after that. I suggest exporting it to ldif (via 'ldbmcat -n > file.ldif' with slapd offline), delete the db, then reimport (via 'ldif2ldbm -i file.ldif') and restart slapd. You will notice a *SERIOUS* speed increase during search and a *SERIOUS* speed loss during the initial import. Unless you're doing tonnes of updates, you shouldn't have any speed issues with updating it, though.
Re:What LDAP have to do with Linux??? (Score:2)
Arguably it is more of a "generic Unix" thing; and actually is pretty usable on a wider set of systems than that.
It's intended to store directory information that would be useful for all sorts of things in terms of system administration on Linux and similar systems; the poster certainly did mention tools widely used on Linux like useradd , userdel, usermod, passwd.
Re:AD (Score:2)
OK Novell isn't a breeze either but they were doing it when MS thought windows 3.1 for workgroups was a server archetecture - it's
oh and documented? don't make me laugh. half thier documentation is marketing materials and the other half is incomplete. Please don't mod this up for being anti-microsoft (i still work w/ ms every day, hell, i'm writing this off w2k server w/ ie), I just had to say that the w2k ad is way more wack than this poster seems to think.
Re:List of OpenSource LDAP Tools and Software (Score:2)
and
<br>
are
your
friends.
Get
to
know
them.
t_t_b