Tool
Buscar
Shameless Plugs
Most Popular
En línea
Inicio de sesión
%count lecturas
LDAP Console
LDAP Console
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.
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()
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!
| Adjunto | Tamaño |
|---|---|
| LDAPConsole.tar_.gz | 493.48 KB |
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
TLS
Submitted by bigbull on 13 May 2008 - 9:48am.
The help file doesnt tell me what switch to use or how to bind securely.
Any ideas?
- Be the first to comment! To leave a comment you need to Login or Register
Hello, Try using server:636
Submitted by rkalfane on 4 June 2008 - 6:34am.
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
- Be the first to comment! To leave a comment you need to Login or Register
2