OpenDJ Error - Connect Error Result Code: 91 (Connect Error)

When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
June 5, 2017
OpenDJLDAPldapsearchForgeRock

This is for an old version of OpenDJ (2.6 to be exact) though that shouldn't matter. Fairly explicit error however it became more of a factor trying to troubleshooting an it needed. It also justified me writing a blog about it knowing that future Daniel comes back and say, 'oh, thanks Past-Daniel!'


Remember, bat for windows!

https://technicalconfessions.com/images/postimages/postimages/_443_2_Result Code 91 connector error.png

Firstly, the ldapsearch.bat is the file that needs to be executed. This can be located within the opendj\bat. A lot of the ForgeRock supports the UNIX commands (which I also prefer) though the bin directory here is redundant.

It's the ldapsearch.bat file and not the ldapsearch file that is needed here. In hindsight, it's obvious. I do feel idiotic writing this though when you're more a unix-than-a-windows-guy (which is a real thing!) and when you're following the ForgeRock documentation, it's not completely obvious. When you execute the .\ldapsearch command though it prompts you with a 'How do you want to open this file?', the first thing that came into mind was an ACL permissions issues


Back to the error

Back to the error, "Connect Error Result Code: 91 (Connect Error)". The LDAP command can be executed using the .bat file though this constantly popped up. This non-ssl connection should always be executed on the LDAP instance itself for obvious reason. Also, this is why you would see examples as having the parameter as -h localhost. This is OK though explicitly indicating the FQN or IP address could resolve this for you.

The next parameter is the username and password. The openDJ control panel can be started and you can use the username/password in there. Again, this is located within the bat directory.

https://technicalconfessions.com/images/postimages/postimages/_443_6_logging in using openDJ control panel.png

Confirming the username/password would eliminate the possibility that it's a credential issues. Then, them there's the port number. Turned out that this was the issue for me. When reviewing the opendj/logs/server.out file, the following was logged.

category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on Administration Connector 0.0.0.0 port 4444. category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAP Connection Handler 0.0.0.0 port 389. category=CORE severity=NOTICE msgID=458887 msg=The Directory Server has started successfully

... This say the classic 389 port number for LDAP. Why was I using 1389. Turned out that the example queries I intended to use indicated a different port number. Again, simple enough though took time to discover such an issue as well as write this blog! Comments below are always welcome

About the author

Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles

Comments

Other Posts

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...
E_WARNING Error in file posts.php at line 464: fopen(http://www.technicalconfessions.com/images/postimages/postIcons/pp444.png): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found E_WARNING Error in file posts.php at line 464: fclose() expects parameter 1 to be resource, boolean given

OpenDJ Error - Connect Error Result Code: 91 (Connect Error)

OpenDJLDAPldapsearchForgeRock

June 5, 2017
Created by: Daniel Redfern
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
Read More...

Tomcat NioEndpoint$SocketProcessor.doRun java.lang.NullPointerException error

TomcatJava-8PKICAS

June 5, 2017
Created by: Daniel Redfern
When initiating the Tomcat instance, the cas-stderr log file will log a SEVERE error logging multiple times every few seconds
Read More...

IDM ERROR - JDBC repository configured but datasource default was not found

ForgeRockIDMJDBC

May 23, 2017
Created by: Daniel Redfern
IDM ERROR - JDBC repository configured but datasource default was not found
Read More...

OpenIDM Issue - javax.crypto.BadPaddingException: Given final block not properly padded

OpenIDMIDMForgeRockcryptography

May 23, 2017
Created by: Daniel Redfern
org.forgerock.json.JsonException: org.forgerock.json.crypto.JsonCryptoException: javax.crypto.BadPaddingException: Given final block not properly padded
Read More...

Validating CAS service tickets - Client available

CASAuthentication

May 23, 2017
Created by: Daniel Redfern
During the CAS integration for a protected web application, there was always the question on how to see the CAS response once someone has authenticated.
Read More...

HOW TO: Enqueue a JMS_TEXT_MESSAGE from java to Oracle database Queue

AQJMSQueueSQL

February 1, 2017
Created by: Daniel Redfern
In this example, I've quickly highlighted the JMS (Java Message Service) components with a simple POJO (Plain Old Java Object) for an asynchronous oracle database queue as well as constructing a JMS_TEXT_MESSAGE to the queue.
Read More...

Shibboleth SP Issue: opensaml::saml2md::MetadataException

ShibbolethIDPShibboleth-SPSAML2metadata

December 13, 2016
Created by: Daniel Redfern
When integrating the Shibboleth IDP and the Shibboleth SP, I would receive the following saml2 metadata issue

opensaml::saml2md::MetadataException
The system encountered an error at
To report this problem, please contact the site administrator atroot@localhost.
Please include the following message in any email:
opensaml::saml2md::MetadataException at (http://HOSTNAME/secure/)
Unable to locate metadata for identity provider (https://HOSTNAME/idp/shibboleth)

Read More...

Shibboleth CAS Integration: HTTP Status 500 - Error processing ShibCas authentication request

ShibbolethIDPCASAuthentication

December 13, 2016
Created by: Daniel Redfern
You need to integrate Shibboleth IDP 3 with CAS This means that Shibboleth uses CAS as the authentication module to authenticate users. This is a Shibboleth IDP external authentication plugin that delegates to CAS
Read More...

OpenDJ Issue - The search base entry 'dc=example,dc=com' does not exist

OpenDJldapsearchForgeRock

November 2, 2016
Created by: Daniel Redfern
This bugged me for a while though when I installed a default openDJ instance in my local computer for POC purposes, I would get an ldapsearch error response stating that The search base entry 'dc=example,dc=com' does not exist All I was doing was a simple ldapsearch so what was the problem.
Read More...