License:
Free

Download LDAPConsole.tar_.gz

LDAP Console

LDAPConsole_screenshot1

Graphical and text mode LDAP Console to connect, search, view, modify objects, create scripts (BeanShell), with auto-completion, variables, aliases and possibility to add new commands using Java or BeanShell scripts.

LDAPConsole_screenshot2

You can easily do searches, view object details using LDIF format (attribute: value), modify attributes with very simple commands.

Try to connect to a LDAP server and search for objects:

  • connect localhost cn=admin,ou=users,o=system mypassword
  • help search
  • search objectClass=user

The command “help” will list all you can do with the tool, grouped by categories (CORE, LDAP, UTILS, others…). It’s easy to create new commands/categories by implementing a Java interface, putting the class in a jar file, and the jar file in the commands folder. All commands are dynamically loaded in the console.

New commands can also be created using BeanShell. For instance, the following will add a file directory list from the console:

  • alias fdir=bsh dir()

LDAPConsole_screenshot3

You can also monitor events that occur in eDirectory by settings “monitor” with a name and a LDAP filter. This could be very useful in IDM projects to monitor all the events generated by connectors for instance.

The whole console can use and be scripted using BeanShell scripts, so there is no limit to extend it.

Have fun!

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

Leave a Comment

  • bigbull says:

    The help file doesnt tell me what switch to use or how to bind securely.

    Any ideas?

  • rkalfane says:

    Hello,

    Try using server:636 as the server name, and maybe add a “true” parameter at the end of the connect command. I will have a look at the source code to tell you how to do it.

    You may also have to import the root CA to the Java JRE in lib/security/cacerts using the keytool utility…

    Cheers,

    Réza

By: rkalfane
Dec 7, 2007
8:00 am
Reads:
1,482
Score:
Unrated