• August 12, 2007

Using OpenLDAP with WebLogic Server

Guest Author

This was originally posted on my dev2dev blog August 12th, 2007.

A customer I was working with this week had some difficulty using Active Directory in conjunction with WebLogic Server Security.  I've always used the Embedded LDAP server that ships with WLS as my user and group store since most of my work is just demos and prototypes, but I thought this would be an excellent opportunity to see what it is like to configure an external LDAP provider.  Since I don't have easy access to Active Directory, I decided to use OpenLDAP.  I am an LDAP newbie and was surprised at the lack of results that I received searching on google for my LDAP 101, but I was able to piece enough information together from wikipedia and other articles to get me going.

Install and configure OpenLDAP

OpenLDAP is typically used on *nix systems, but my laptop runs Windows XP.  I was able to find someone that makes a Windows Distribution and I retrieved version 2.2.29.  It's very straight forward to download and install it as a Windows Service.  Similar to Apache's httpd.conf file, the sldapd.conf in the base directory is the master configuration file.

I had to change two things about my file.  At the top, I added support for additional schemas based on advice on an email thread.  It seems like it is very common to use the inetOrgPerson object class based off of my limited shoulder surfing at customer sites, so I added support for that and one other one named cosine.


# See slapd.conf(5) for details on configuration options.

# This file should NOT be world readable.


ucdata-path ./ucdata

include ./schema/core.schema

include ./schema/cosine.schema

include ./schema/inetorgperson.schema

At the very bottom of the sldapd.conf file, you should see a few other things to configure.

database    bdb

#suffix "dc=my-domain,dc=com"

suffix "dc=bea,dc=com"

rootdn "cn=Manager,dc=bea,dc=com"

# Cleartext passwords, especially for the rootdn, should

# be avoid. See slappasswd(8) and slapd.conf(5) for details.

# Use of strong authentication encouraged.

rootpw secret

# The database directory MUST exist prior to running slapd AND

# should only be accessible by the slapd and slap tools.

# Mode 700 recommended.

directory ./data

# Indices to maintain

index objectClass eq

So what this section says is that OpenLDAP will use BDB as it's database and store the information in the data directory.  These are defaults.  This was helpful to know as I messed up my database a few times playing around with various settings and could always just stop OpenLDAP, delete the data directory and start OpenLDAP to start from a clean slate.  The default suffix for entries typically follows the domain name conventions, so in this case I used bea.com where the DC stands for Domain Component.  This site has additional definitions for the other LDAP abbreviations like CN (Common Name) and SN (Sir Name).  The default for the root user name is Manager and the password defaults to secret.  Of course in a real production setting you would want to encrypt this password, but for my demo purposes, this works fine.  Now I started the Windows Service, executed a netstat command and observed that I was now listening on the LDAP port of 389 and was up and running.

Add Users and Groups

When you first start OpenLDAP, there is no user/group structure provided, you have to add those entries yourself.  LDAP uses the LDIF format to import and export entries into LDAP.    I was able to find some examples and modify them to have a user/group structure that worked for my example purposes.  Like I said, I'm an LDAP newbie, so do not consider this a recommended structure for your enterprise, but it worked for me to store both users and groups in a very basic way.  I'll show you a tool that you can use later to do this visually, but it's helpful to know what's going on under the covers so you understand what the tool is doing.

dn: dc=bea,dc=com

dc: bea

objectClass: top

objectClass: domain

dn: ou=people,dc=bea,dc=com

ou: people

objectClass: top

objectClass: organizationalUnit







dn: ou=groups,dc=bea,dc=com

ou: groups

objectClass: top

objectClass: organizationalUnit

dn: cn=groupA,ou=groups,dc=bea,dc=com

objectClass: top

objectClass: groupOfNames

cn: groupA

member: cn=jbayer,ou=people,dc=bea,dc=com

Above are the contents of a file I called base.ldif.  Here I define two organization units, people and groups.  Under people I have a user single user named jbayer and under groups I have one group named groupA, of which jbayer is a member.  To import this into OpenLDAP, I just use the ldapadd command as shown below.


C:\Program Files\OpenLDAP>ldapadd.exe -f base.ldif -xv -D "cn=Manager,dc=bea,dc=com" -w secret

ldap_initialize( <DEFAULT> )

add dc:


add objectClass:



adding new entry "dc=bea,dc=com"

modify complete

add ou:


add objectClass:



adding new entry "ou=people,dc=bea,dc=com"

modify complete

add objectClass:


add cn:


add sn:


add uid:


add userPassword:


adding new entry "cn=jbayer,ou=people,dc=bea,dc=com"

modify complete

add ou:


add objectClass:



adding new entry "ou=groups,dc=bea,dc=com"

modify complete

add objectClass:



add cn:


add member:


adding new entry "cn=groupA,ou=groups,dc=bea,dc=com"

Using an LDAP Browser

Since doing all this command line stuff isn't very visual, you can also use this Java LDAP Browser to view/modify OpenLDAP entries and to validate that your entries got imported correctly.  Dowload the tool and use connection settings similar to mine shown below (click the thumbnail to get a larger view), which should result in you being able to connect and browse the tree.  You can also use this tool to add and edit entries, but I won't cover that here.  Edocs also has instructions on how you can use this same tool to browse the Embedded LDAP server that comes with WLS.


openLdapConfig ldapBrowser [3]

Configure WebLogic Server

By default, WebLogic Server uses an security realm called myrealm that uses the Embedded LDAP server configured with the Default Authenticator.  In order to add OpenLDAP as a source, you have to configure an additional Authentication Provider to the realm.  Here are the steps for configuring WLS 10, although the steps are similar with other WLS versions.

  1. Login to the WLS console - my example servier is at http://localhost:7001/console  with user weblogic and password weblogic
  2. Browse to Security Realms->myrealm
  3. Click on the Providers tab
  4. Browse to the Authentication section
  5. Click the Lock and Edit button
  6. Click the new button and select OpenLDAPAuthenticator and give it a name, I chose openLDAPAuthenticator
  7. Click on the newly created Authenticator and select the Provider Specific tab
  8. I changed the following settings from the provider specific defaults based on the values I loaded in the ldif file shown earlier:

Group Base DN:  ou=groups,dc=bea,dc=com

Static Group Object Class: groupOfNames

User Base DN: ou=people,dc=bea,dc=com

User Object Class: inetOrgPerson

Principal: cn=Manager,dc=bea,dc=com

Host: localhost

Credential: secret

Confirm Credential: secret

Static Group DNs from Member DN Filter: (&(member=%M)(objectclass=groupOfNames))

User From Name Filter: (&(cn=%u)(objectclass=inetOrgPerson))

Group From Name Filter: (&(cn=%g)(objectclass=groupOfNames))

One Major Gotcha - Setting the Default Authenticator to something other than "Required"

Now you can save and Active the session.  WebLogic Server needs to be restarted for changes in the Authenticator to take effect, but before you restart there is one other change we have to make.  Authenticators have an attribute named Control Flag.  The value is either REQUIRED, REQUISITE, SUFFICIENT, or OPTIONAL.  See the help in the console for detailed explanation of these values.  The Default Authenticator has a default value of REQUIRED that should be changed to either SUFFICIENT or OPTIONAL in order for users that are only OpenLDAP to be able to login to with the WebLogic Security Framework without also having to be in Embedded LDAP.

After restarting, log back into the console, browse to your realm and select the Users and Groups tab.  You should see the user you added.  If you select a user from OpenLDAP you should be able to change their password as well as see their group membership if everything is configured properly.



Secure a web application

You can try it out by creating a simple web app with a security-constraint element in web.xml entry as follows that defines a role named SecuredUser and uses it to protect all resources in the web app:







Then in your weblogic.xml define element to add an security-role-assignment element to a specific user.




If you would rather use LDAP groups to specify the role assignment, which is much more likely to be the case, then you would use a section like this in your weblogic.xml.



In this case, instead of explicitly naming all of the users you want in that role in each web applications deployment descriptors which is not a very good practice for an enterprise, the role SecuredUser will be assumed to be a Global Role defined in your realm's Roles and Policies -> Global Roles.  In the console, you can assign the Global Role SecuredUser to all users with membership in groupA for example.

What if you want to find out additional LDAP attributes other than users and groups and use them in your applications?  In a subsequent post I plan on showing how to use an LDAP control to do that or use the Unified User Profile feature of WebLogic Portal to automatically stuff those values in the user profile.

Join the discussion

Comments ( 16 )
  • V&iacute;ctor Glez. Wednesday, June 3, 2009

    I followed the steps in the tutorial.
    I have SQL Authenticator(Default Authenticator) as OPTIONAL and the new OpenLDAP Authenticator as REQUIRED
    Now I have the problem that I can not sign with the new user (jbayer) in WLS

    <02-jun-2009 17H44' CEST>
    <02-jun-2009 17H44' CEST> weblogic.security.SecurityInitializationException: User jbayer is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
    at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace

    What are the groups that should belong to the user to log in as administrator WLS?
    Is this possible?
    Thank you
  • James Bayer Wednesday, June 3, 2009
    Victor, only users in certain roles such as Admin or Operator can start the server, and to map to those roles, you need to be in certain Groups in the Authentication Provider. This is documented here:
    Did you put your jbayer user in the Administrators group or modify your Admin role to include jbayer?
  • Javier Wednesday, July 15, 2009
    Hi James
    I have the same problem, but how can i modify the roles if i can't start the server?? I had only a administrator and now i can't start because i have this problem
  • James Bayer Wednesday, July 15, 2009
    Try to revert to the embedded LDAP (Default Authenticator) user that was in your server's boot.properties file at the time the domain was created. By default this is named "weblogic" unless you change it. Then you should be able to start the server and make any adjustments to the roles, etc with the users from the Open LDAP Authenticator.
  • Steve Neal Tuesday, August 25, 2009
    I'd been fiddling with the LDAP settings all day trying to get this working . I hadn't realised that the gotcha with the Default Authenticator had been causing the problems all along and that the settings I'd been using were fine.
    Thanks very much for posting this article, saved me a sleepless night!
  • Prashant Friday, November 27, 2009
    Hi James,
    This is very good article for ldap newbie like me, we were search for moving from iplanet directory to open source directory like OpenLdap with weblogic 9.2. This give a overview how we can start with.
  • Maxence Button Wednesday, December 2, 2009
    Hey James :)
    Long time no see !
    Hope you're doing well in the windy city.
    I'm currently working on integrating OpenLDAP with a WLS 10. (by the way, I thought it was a good subject for my blog, and then I found yours which deals with pretty much the same thing I was going to write about :) )
    In your example, you're hitting the group "ou=people,dc=bea,dc=com" as the User Base DN to retrieve the users which will be visible in your domain. My concern is about subgroups. Following your example, I would like to authorize only the people whith a Group-A membership to appear in the console (in my case, the general "people" group has more than 100 000 entries ...)
    There's so many configurations possible, that I'm wondering whether, by any chance, you had to fit a similar requirement.
    A workaround would be to flag, with a specific attribute, all the users belonging to Group-A and then filter them with "User From Name Filter" field but it would imply that the whole list has still to be read, which is what I'd like to avoid.
    I'm still working on it, I guess I'll find a solution, but if you have any clue for me to save time, that would be cool.
    Thanks and nice work, as usual, friend :)
    Kind regards.
  • james.bayer Wednesday, December 2, 2009
    I really don't think the size of the org should matter too much as I think the console paginates the users. For example, I'm pretty confident that the entire Oracle internal LDAP directory is used with WebLogic Server. Now if your requirement is definitely not to even show other users in the console regardless of which role you map to them, then as you mention I think the User From Name Filter might work for you. You would have to ask someone like Josh Bregman to be sure, but I'm pretty confident that the LDAP servers can handle that filter efficiently. Let me know if you find out the solution.
    Good luck,
  • npissan Wednesday, June 22, 2011

    Hi, just run on this very interesting blog. Would like to ask you if this architecture would help me from crashing my ldap server. My openLdap whenever a code error in my apps opens more than 500 connection at a min it crashes, so i guess it would be a better approach WL connect to ldap once and handle all the request. Is that possible?Thanks in advance.

  • james.bayer Wednesday, June 22, 2011

    Nick, I'm not sure how many OpenLDAP connections would be opened by default by the WLS Open LDAP Authenticator. You could ask in the OTN WLS Security forum or Oracle Support for clarification.




  • Pradeep Tuesday, July 5, 2011

    Hi James

    I successfully integrated the Novell e-directory and weblogic 9.2.2.

    I am able to see all the user and group from novell in weblogic console.

    Now, I have 2 cases:

    Case 1: When I am giving admin roles to a user called abc (abc is a member of group called admins in Novell). I can log into the console successfully.

    Case 2: I removed the admin role of user called abc, and gave admin role to group called admins. Now, when I am trying to log into console using the credentials of abc ( 'abc' is member of 'admins' in Novell). I am getting access denied. I did some research and found that weblogic is sending query to novell and getting authentication, but its not trying to get authorization. I mean its not sending query to Novell to find out, which group abc belongs to?

    Do you know how to resolve it? I am stuck with it from last 2 months. I will really appreciate if you can help me out.

    Please let me know if you need more detail on it.

    Thanks in Advance !!!

  • pradeep Tuesday, July 5, 2011

    FYI: abc is just like user jbayer and admins is like group, groupA in your case.

    Also, for giving admin roles I am going to Security realms-->my realm-->Roles and Policies-->relam roles--> Global roles--->Roles-->Admin

    Add conditions-->Group(select)-->Next-->Group Argument Name--> Add--> finish

    Please let me know if you need more detail on it.

    Thanks in Advance !!!

  • james.bayer Tuesday, July 5, 2011


    You can enable more verbose logging for the WLS security sub-system to see the WLS perspective of what is happening. It's likely that the authenticator is not correctly configured to return the groups for each user, but is configured to list all the groups. I recommend working with Oracle Support to work through this as it can be somewhat tedious if you're not familiar with LDAP syntax. You could also try posting in the WLS Security OTN forum:


    I recommend that you describe the LDAP layout and how you have the authenticator configured. I'm really not an expert in this area so Support/OTN will better serve you.

    Thanks, James

  • Pradeep Tuesday, July 5, 2011

    Thanks James, for your quick and positive response.

    I already enabled the debug flag for security ( atz and atn). That is how I found that its getting authentication but failed on authorization.

    Also, I opened SR to oracle but they are very slow for support cases.

    Anyways, thanks for the blog, it is really informative.

    Keep it up !!!

  • Vivek Tuesday, July 26, 2011


    I am new to LDAP.

    I have installed OpenLDAP in RedHatLinux 5.4, while adding new user it gives below error,

    ldap_add: Protocol error (2)

    additional info: no attributes provided

    And tell me how can I cross check the users with LDAP browser.



  • james.bayer Tuesday, July 26, 2011

    Vivek, I don't know my LDAP all that great either. I recommend looking at this post that shows a nice LDAP Explorer http://blogs.oracle.com/jamesbayer/entry/look_inside_weblogic_server_emand perhaps posting your question with OpenLDAP experts like StackOverflow or similar. Good luck, James

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.