Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7635841
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T07:31:40+00:00 2026-05-31T07:31:40+00:00

We are writing an application that shall connect to different LDAP servers. For each

  • 0

We are writing an application that shall connect to different LDAP servers. For each server we may only accept a certain certificate. The hostname in that certificate shall not matter. This is easy, when we use LDAP and STARTTLS, because we can use StartTlsResponse.setHostnameVerifier(..-) and use StartTlsResponse.negotiate(...) with a matching SSLSocketFactory. However we also need to support LDAPS connections. Java supports this natively, but only if the server certificate is trusted by the default java keystore. While we could replace that, we still cannot use different keystores for different servers.

The existing connection code is as follows:

Hashtable<String,String> env = new Hashtable<String,String>();
env.put( Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory" );
env.put( Context.PROVIDER_URL, ( encryption == SSL ? "ldaps://" : "ldap://" ) + host + ":" + port );
if ( encryption == SSL ) {
    // env.put( "java.naming.ldap.factory.socket", "CustomSocketFactory" );
}
ctx = new InitialLdapContext( env, null );
if ( encryption != START_TLS )
    tls = null;
else {
    tls = (StartTlsResponse) ctx.extendedOperation( new StartTlsRequest() );
    tls.setHostnameVerifier( hostnameVerifier );
    tls.negotiate( sslContext.getSocketFactory() );
}

We could add out own CustomSocketFactory, but how to pass information to that?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T07:31:41+00:00Added an answer on May 31, 2026 at 7:31 am

    For others have the same problem: I found a very ugly solution for my case:

    import javax.net.SocketFactory;
    
    public abstract class ThreadLocalSocketFactory
      extends SocketFactory
    {
    
      static ThreadLocal<SocketFactory> local = new ThreadLocal<SocketFactory>();
    
      public static SocketFactory getDefault()
      {
        SocketFactory result = local.get();
        if ( result == null )
          throw new IllegalStateException();
        return result;
      }
    
      public static void set( SocketFactory factory )
      {
        local.set( factory );
      }
    
      public static void remove()
      {
        local.remove();
      }
    
    }
    

    Using it like this:

    env.put( "java.naming.ldap.factory.socket", ThreadLocalSocketFactory.class.getName() );
    ThreadLocalSocketFactory.set( sslContext.getSocketFactory() );
    try {
      ctx = new InitialLdapContext( env, null );
    } finally {
      ThreadLocalSocketFactory.remove();
    }
    

    Not nice, but it works.
    JNDI should be more flexible here…

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm writing a small multithreaded client-side python application that contains a small webserver (only
I'm writing a small c# console application that needs to interogate Websphere Application Server
I writing an application that pushes data over an external service to some server.
I am interested in writing an application that overlays a small heads up display
I am writing a small application that does a lot of feed processing. I
I'm thinking about writing a small application that will help me mass rename files.
I'm writing a small .NET application that can produce SWF files, and I need
I'm writing a small C application that launchs a Matlab script (.m file). I
I'm writing a small application in C that reads a simple text file and
I am writing a small application with Qt 4.6 (64-bit Arch Linux, though that

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.