Skip to Content

This documents describes how to install and configure a LDAP server in the SUP at AWS instance. The LDAP server used in OpenDJ. This document is about installation and configuration only, not about administration or SUP configuration.

Pre-requisites

SUP can use a LDAP server for authentication (and / or authorization). Normally SUP comes with OpenDS, but there are many reasons not to use it. A good oe is that OpenDS is not part of the SUP AWS image. To authorize device users against a LDAP server you can either configure the Windows 2008 server SUP is running on to be an Active Directory Server (ADS) or install a 3rd party LDAP server. As there are many open, free and easy to run LDAP servers available, let’s use OpenDJ. This server can be seen as the replacement of OpenDS and because of its history comes with a wide and complete feature set.

System configuration

Configure the system variable JAVA_HOME to include Java. You can use the Java version SUP uses: C:\Sybase\UnwiredPlatform\JDK1.6.0_31-x64.

Install OpenDJ

Download and unzip OpenDJ in a directory of your choice where you want OpenDJ to be run from. The server is based on Java and does by default not write any system configuration to the registry, so it’s a portable server. As OpenDJ can be configured to be a Windows service, make sure that the path is stable and you won’t have to change it.

Example: C:\Dev\OpenDJ

Configure OpenDJ

Start the OpenDJ setup: setup.bat from the root directory of OpenDJ. The configuration wizards is very easy to use and guides you to a very simple installation process where you only will have to define the admin password and that OpenDJ should be configured as a Windows server.

Welcome screen

/wp-content/uploads/2012/08/opendjinstall1_129774.jpg

Check the host name and port. 389 is a default LDAP port and 4444 the default admin port of OpenDJ. The admin user is named cn=Directory Manager. Give a password you can remember.

/wp-content/uploads/2012/08/opendjinstall2_129775.jpg

As you do not want to make it too complicated, this is going to be a standalone LDAP server.

/wp-content/uploads/2012/08/opendjinstall3_129788.jpg

Give the base DN a meaningful name, like dc=sup,dc=com.

/wp-content/uploads/2012/08/opendjinstall4_129789.jpg

The default runtime options are more than enough. If you are worried about memory consumption you can define some limits here. For the rest: just click on next.

/wp-content/uploads/2012/08/opendjinstall5_129790.jpg

Check the configuration parameters and if you want to start OpenDJ at startup of the AWS SUP instance, select: “Run the server as a Windows Server”.

/wp-content/uploads/2012/08/opendjinstall6_129791.jpg

The wizards start to configure OpenDJ.

/wp-content/uploads/2012/08/opendjinstall7_129792.jpg

In the end you should see a message indicating that the configuration is completed.

/wp-content/uploads/2012/08/opendjinstall8_129793.jpg

Now OpenDJ is already up and running and can be used.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply