Luma - LDAP browser, utility and more.
So, you've got Luma installed and running already? Good for you. Now comes the part of configuring how to communicate with your server(s).
From the 'Settings' menu, choose 'Edit Server List' (or Ctrl-E)
Click 'Add' to add a new ServerConnection-object
Then you should get a dialog like this:
Choose a descriptive name for your connection. It can be the hostname, or just jibberish.
In this example, we name it 'Demo'
In the next screenshot, we get to actually put in some real connection-data
Our demo-server, is configured with tls/ssl-support, and we connect _with_ TLS-options. Only
connecting using TLS/SSL will make the 'Certificates'-branch in the Server-window show. Try enable/disable
and see for yourself.
Next screenshot is where we choose by whom do we connect as. This example uses anonymous authentication.
If you want to do writes onto your LDAP-server, you need to specify a valid DN (distinguished name), e.g.
cn=admin,dc=mydomain,dc=com. Unless you know what SASL is, chances are - you're most likely to be using simple authentication
with a binddn and a password. Writes requires identification, unless you've configured your server to do otherways.
You can either choose to supply a root-node for your server (suffix) - or you can let Luma
automatically fetch it from your server. If this fails, its either an issue with ACLs - or
Luma doesn't support your vendor's server-implementation for fetching base-suffixes.
Luma supports the standard certificate-options supplied by OpenLDAP. Our experience is that most people
are happy with setting this option to 'allow' or 'demand'.
Whoa - you're now good to go having fun with Luma. Click 'Choose plugin' at the top - and start playing around.
We suggest you start with the browser-plugin (Look'n' feel of directory explorers).
For documentation on how to use the different plugins, go back to the documentation-page either via the menu
or just here.