Home/ Questions/Q 3451902
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T09:11:44+00:00

I’ve setup up a Security Realm in Glassfish to authenticate against an Active Directory

  • 0

I’ve setup up a Security Realm in Glassfish to authenticate against an Active Directory server. The configuration of the realm is as follows:

Class Name: com.sun.enterprise.security.auth.realm.ldap.LDAPRealm
JAAS context:  ldapRealm
Directory: ldap://172.16.76.10:389/
Base DN:  dc=smallbusiness,dc=local
search-filter: (&(objectClass=user)(sAMAccountName=%s))
group-search-filter: (&(objectClass=group)(member=%d))
search-bind-dn: cN=Administrator,CN=Users,dc=smallbusiness,dc=local
search-bind-password: abcd1234!

The realm is functional and I can log-in, but when ever I log in I get the following error in the log:

SEC1106: Error during LDAP search with filter [(&(objectClass=group)(member=CN=Administrator,CN=Users,dc=smallbusiness,dc=local))].
SEC1000: Caught exception.
    javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=smallbusiness,dc=local'
        at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2820)
        ....
        ....
ldaplm.searcherror

While searching for a solution I found that it was recommended to add java.naming.referral=follow to the properties of the realm. However, after I add this it takes 20 minutes for GlassFish to authenticate against Active Directory. I suspect it is a DNS problem on the Active Directory server. The Active Directory server is a vanilla Windows Server 2003 setup in a Virtual Machine.

Any help/recommendation is highly appreciated!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This was maddening trying to solve this… Glassfish 3.0.1 trying to connect with Windows, and getting the above error.

    I’m not a Windows or LDAP whiz at all… but finally found this:

    http://forum.springsource.org/showthread.php?t=87673

    And the very last line is the key: use the “Global Catalog Port” – instead of 389, it is 3268 by default. And the exception disappears.

    Why?

    Who cares?

    (well, ok, I’m going to read about it now.)

    • 0