Softerra Ldap Browser Download
Softerra Ldap Browser Search User
Softerra Ldap Browser Mac

Softerra is the company that brought you the greatest hits of IAM solutions: Adaxes and LDAP Administrator. We also provide custom software and hardware development as well as R&D services. If an LDAP server blocks access to its RootDSE, its type is defined as Not Available. LDAP URL is an informational field that is automatically updated as soon as you apply the modified settings of the profile. LDAP URL holds complete information about the connection, server host and port, base DN, displayed attributes and search filter.

FAQ is the first place to look at if you want to find out more about what using Softerra LDAP Administrator is really like. Below you'll find answers to most frequently asked technical questions usually associated with our product.

No, it doesn't. If you want to use version 2008, please upgrade.

For basic HTML View customization, you have to be familiar with HTML and XML. Advanced HTML View customization may require XSLT and JavaScript experience. For further details, please take a look at the HtmlView folder located in 'C:Program FilesCommon FilesSofterra SharedLDAP Administrator 3' for LDAP Administrator 3.x and C:Program FilesSofterraLDAP Administrator 4 for LDAP Administrator 2008.

By default, LDAP Administrator uses the local application data folder to store its configuration files, like metabase and schema cache. Such behavior can cause problems for those using roaming profiles in their network.

Open registry editor (Start->Run->regedit.exe)
Navigate to or create registry key
- HKEY_LOCAL_MACHINESOFTWARESofterraLDAP Administrator 3Settings - for version 3.x
- HKEY_LOCAL_MACHINESOFTWARESofterraLDAP Administrator 4 - for version 2008.x/2009.x (aka 4.x)
Create a non-zero DWORD value here called EnableApplicationDataRoaming

You can use the HKEY_CURRENT_USER registry hive as well if you want to change the location of application data files only for specific users. In case both registry entries are used, the value from HKEY_LOCAL_MACHINE has a priority over the value from HKEY_CURRENT_USER.

The method described above applies only to Softerra LDAP Administrator version 3.4 (build 1700) and higher.

Where does the application store my profiles?

How can I copy or back up my profiles?

Do I need to back up my profiles when reinstalling LDAP Administrator?

Softerra LDAP Administrator 2.X and Softerra LDAP Browser 2.X store profiles in the registry under the [1] and [2] registry keys respectively. Softerra LDAP Administrator 3.X keeps them in a file called metabase.stg, which is located in the application’s configuration folder [3].

You can copy or back up your version 2.X profiles using the Windows Registry Editor tool. To copy version 3.X profiles, just copy the metabase.stg file from [3]. Note: this file is not human readable, so it can't be read or manually edited. To copy your profiles from one workstation to another, just copy the existing metabase.stg file into the appropriate folder on the target workstation.

You don't need to back up/restore your profiles when reinstalling Softerra LDAP Administrator because they do not get removed during the uninstallation.

HKEY_CURRENT_USERSoftwareSofterraLDAP Administrator
HKEY_CURRENT_USERSoftwareSofterraLDAP Browser
C:Documents and Settings%LOGINGUSERNAME%Local SettingsApplication DataSofterraLDAP Administrator 3

Softerra Ldap Browser Download

At some moment LDAP Browser experiences a considerable slowdown, so you have to wait 2-3 seconds before it adds a new node into the left-hand side tree view panel.

Incorrect DNS setting or complete absence of DNS.

Change your DNS settings so that the client and server hosts have both direct and reverse resolving via DNS enabled. Another possible solution could be adding required records to the hosts (lmhosts) file.

An error occurs while attempting to install LDAP Browser/LDAP Administrator and the installation process is abandoned.

The reason for the above is usually one of the following:

The installation package has been corrupted/damaged during download.
You are not duly authorized to install the applications to your system.
Your hard drive has run out of free space or your disk quota is exceeded.
You don't have permissions to write to the application destination folder.

To make sure the installation package is not damaged, you need to check its MD5 hash sum. To calculate MD5/SHA1 hash, you can use one of the free hash calculators available. After getting the package's MD5/SHA1 hash sum, you then need to compare it to the original one provided at the download page. If MD5/SHA1 hash differs in any way, this means that the package is corrupted and has to be downloaded anew. Please note that the damaged package might have been cached by your proxy servers chain or by your web browser local cache, so it's strongly recommended you disable your proxy and clear the browser cache before a repeat file download.
Make sure you are duly authorized to install applications and to write to the filesystem.
Check if your hard drive has enough free disk space. Perform a temporary directory cleaup, if necessary. It's recommended you have at least 20 Mb free disk space of the destination drive to ensure successful installation.

This article concerns LDAP Administrator versions 2.x or LDAP Browser versions 2.x. Having an LDAP server profile created with the SSL configuration enabled, you still can't connect to the server. As a result, '[error 81] Can't contact LDAP server' is displayed.

This kind of behaviour occurs due to the absence of necessary SSL certificates in the certificate database, or the absence of the certificate database itself. This certificate database is required for an LDAP client library to establish the SSL connection.

You should create and populate a certificate database containing the necessary certificates manually.To do this, please follow the procedure below:

Download and install the Netscape web browser version 4.x. Note that it's vital to use version 4.x - later version like 5+ or Firefox use newer certificate store format which is incompatible with the version used by LDAP Browser 2.x.
Run the Netscape browser.
Open URL: https://yourserver:sslport/, where:
- yourserver - Your LDAP server address, provided it is an IP or host name. For example: 192.168.234.33 or ldap.mycompany.com.
- sslport - A TCPIP port number used by your server to accept SSL connections. Usually his port number is 636.
You'll see the Netscape Certificate Name Check window. Follow the instructions provided there and accept the server certificate for this and future sessions.
Close the Netscape browser
Copy the key3.db and cert7.db files from the Netscape user profile directory to the LDAP Administrator or LDAP Browser root directory.
Restart LDAP Administrator or LDAP Browser.
Open the server profile.
Change Port number at the General tab. Press Apply.
Check the Try to use SSL box at the LDAP Settings tab. Press Apply.
Press OK.

I have found a problem/a bug. Where can I report it to?
I'd like to make a suggestion. Who can I send it to?
I've come across a problem and can't find a solution. What do I do?

If you have found a problem or a bug, please send us a report. Try to include as much hardware (CPU, RAM, Motherboard, Video) and software (OS version, Service pack, Internet Explorer version, MS Office version, LDAP Administrator version) information of yours as possible along with the description/instructions to help us reproduce the problem.

To send a bug report or a suggestion, you can use the built-in functionality of LDAP Administrator or LDAP Browser. Open the Help menu and choose the Bug report or the Suggestion menu item featured therein.If you come across a problem, first please look through the FAQ section hereof for the solution, or consult help supplied with the application. In case you are still unable to cope with the p