Solved

LDAP Serach Error - NotContextException

Forum|Forum|9 years ago
November 2, 2016
15 replies
12494 views

Hi All,

We are upgarding from CQ5.6.1 to AEM 6.2. In the earlier version we had a code that search the content of Ldap using javax.naming.directory* classes.

Like the way

DirContext ctx = new InitialDirContext(env); //Creating context NamingEnumeration<SearchResult> ldapResults = ctx.search(base.get(), filter, sc); //Calling search method with arguments, this line throws Exception

When we are running the same code in AEM 6.2, getting the error.

javax.naming.NotContextException: Not an instance of DirContext at javax.naming.directory.InitialDirContext.getURLOrDefaultInitDirCtx(InitialDirContext.java:111) at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:267)

Any one faced this issue? The only difference I know is that in Cq5.6.1, we used to do the LDAP configs at server level, in AEm 6.2 they are available in OSGI configs.

Note:- We are defaining the LDAP enviornment varaibles in the Java class as well where we are getting the exception

Thanks

Monika

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by Sham_HC

Hi Monika,

Osgi is an JNDI implementation does not interact well with factory DirContext or LdapContext for casting it back. You can find couple of issue in web on this with various osgi providers. To over come this make use of enhanced LDAP API which replaces JNDI and the existing LDAP API like "schema aware" API with convenient ways to access any LDAP server.

Thanks,

Sham_HCAccepted solution

Hi Monika,

Osgi is an JNDI implementation does not interact well with factory DirContext or LdapContext for casting it back. You can find couple of issue in web on this with various osgi providers. To over come this make use of enhanced LDAP API which replaces JNDI and the existing LDAP API like "schema aware" API with convenient ways to access any LDAP server.

Thanks,

M

monikaa6Author

Thanks Sham. Thats very helpful!!

D

Dineshkumar_L

Hi Sham, Monika,

I am trying to use LDAP API 2.0 in AEM 63 SP2 for our requirement. My maven build is getting succeed but bundle is not getting resolved after uploading it to felix console. Below highlighted packages are not getting resolved. Did you face similar issue?

org.apache.directory.api.ldap.model.exception -- Cannot be resolved

org.apache.directory.ldap.client.api -- Cannot be resolved

Thanks,

Dinesh Kumar L.

J

Jon-Starling

I have this same issue

org.apache.directory.ldap.client.api -- Cannot be resolved

did you ever get it solved?

I have read you can take any jar and wrap it to for use as a bundle but I really want this to be self contained.

Thanks

D

Dineshkumar_L

I have embedded the jar inside my bundle to solve this issue. I could not get through any other options.

Regards,

Dinesh kumar L.

J

Jon-Starling

Thanks for the quick reply! I have made a couple of attempts at that, but I am also fairly new to maven. Can you let me know how you achieved this or point me in the direction of an online guide.

Thanks again.

D

Dineshkumar_L

Yeah, I could recollect it was not that easy. Even embed has introduced some other collision after installing it in OSGI container. So, I had to add some not conditions under the import package too along with embed jar list. Open your Core POM.xml and update it as highlighted below under <Embed-Dependency> and <Import-Package> sections.

Regards,

Dinesh kumar L.

J

Jon-Starling

That's great, thanks I got it to not error, now if I can just figure out why the connection statement is dying without throwing an exception... LOL

Seriously though, really appreciate the help!

Nitin_laad

Community Advisor

Hi Jon, Dinesh,

Facing the same dependency issue you have faced.

tried to resolve using below jar files but no luck.

Embed dependency as part of bundle and remove some from import, as suggested by Dinesh

Can you please have a look and suggest whether I am using correct jar and version.

Using AEM 6.4 sp4 version.

I was able to resolve dependency issues after creating separate bundles, but when invoking the servlet getting "no class definition found issue for LdapConnectionConfig.

Thanks,

D

Dineshkumar_L

Hi Nitin,

Try adding the dependencies as listed in the below snaps:

In Main POM.xml: