Hello Friends,

I am trying to connect WAS 7.0 ND to the LDAP server.However I am getting the following error when I try to test the connection

SECJ7340E: Exception raised trying to connect to LDAP server: NamingException: ldap_server_ hostname:port no; socket closed null.

But I am able to telnet to the ldap server and the ping test for it is also successful.

Can anyone shed some light on this?
It's a bit urgent so any thoughts on this ?

Thanks,
Kushal

Hi Kushal,

   Can you put the SystemOut.log when you a testing? and Fixpack Level

  What's the LDAP error code?

   Is standalone LDAP or federate repository?

   Is connection to a secure/unsecure port (636/389)?

   Check the credentials to connect/binding user/password.


Regards,

Hi Gabriel,

Its a standalone LDAP server with port 636.
Also,the user credentials are correct.

the WAS details are:
Installed Product
--------------------------------------------------------------------------------
Name                     IBM WebSphere Application Server - ND
Version                  7.0.0.23
ID                       ND
Build Level              cf231218.02
Build Date               4/30/12
Architecture             PPC64

I am unable to find any information in the Systemout logs for deployment manager and the nodeagent.

Ok in that case review do you have imported LDAP SSL certificate issuer CA in WebSphere trust repository and the WAS certificate issuer CA imported in LDAP SSL trust repository.

If you haven't the CA public certificate interchanged I think that it can't stablish the connection in secure. That is the reason of "socket closed null".

The first step is to interchange CA certificates.

and where are you getting "SECJ7340E: Exception raised trying to connect to LDAP server: NamingException: ldap_server_ hostname:port no; socket closed null."?

look at the ffdd logs (\profiles\\logs\ffdc)

Are you getting some input in LDAP server logs?

regards,

 Hi Kushal

   Look in this redbook steps you need to configure secure LDAP communication:
   
   WebSphere Application Server V7.0 Security Guide
      www.redbooks.ibm.com/abstracts/sg247660....
      5.2.2 Securing LDAP communication

regards,

Hi Gabriel,

Thanks for providing quick help on the issue.
However my supervisor informed me that we would be implementing federated repository instead of standalone LDAP server for the WAS security and so I had to abandon my efforts on configuring this one.
This would be a one off case where we would be having a federated repos intead of standalone LDAP server.
The federated repos config was taken care of by my colleague who came in the next shift and I missed out on the chance to configure it myself.


Thanks & Regards,
Kushal S. Chaudhary    
    

Hi Kushal,

  Only for your information.

  Although you configure federate repository take in mind that if you need to configure an LDAP SSL server in the federate  repository the step are the same, that is when you add to federate repository an LDAP server the configuration form is very similar that you are using to configure stand-alone LDAP. So the steps of the redbook still applicable.

Kind regards