[
http://issues.apache.org/jira/browse/DERBY-870?page=comments#action_12367230 ]
Sunitha Kambhampati commented on DERBY-870:
-------------------------------------------
I tried with 'no' additional jars and I could get LDAP authentication to work
with derby with
ibm142,jdk142,jdk15
But with jdk141, ibm141, and ibm13- I get the following error
This is what is in the DirContext.
{java.naming.provider.url=ldaps://xyz.abc.com:636,
ava.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory,
java.naming.security.authentication=simple}
ERROR 08004: Connection refused : javax.naming.NamingException: Cannot parse
url: ldaps://xyz.abc.com:636 [Root exception is java.net.MalformedURLException:
Not an LDAP URL: ldaps://xyz.abc.com:636]
Not sure if this is related to since this is secure ldap.
Has anyone else tried it out with 1.3.1 or 1.4.1 vms successfully. If so,
please share your results. Thanks.
> Update documentation on setting up LDAP user authentication.
> ------------------------------------------------------------
>
> Key: DERBY-870
> URL: http://issues.apache.org/jira/browse/DERBY-870
> Project: Derby
> Type: Improvement
> Components: Documentation
> Versions: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.2.0.0, 10.1.2.0,
> 10.1.1.1, 10.1.1.2, 10.1.2.1, 10.1.3.0, 10.1.2.2
> Reporter: Sunitha Kambhampati
> Priority: Minor
>
> http://db.apache.org/derby/docs/dev/devguide/rdevcsecure608.html
> This talks about needing jndi.jar , ldap.jar and providerUtil.jar.
> I think this is not true anymore with the latest 1.4.2 vms atleast, and
> should be updated. It seems like with 1.4.2 etc, all these classes are in
> rt.jar. Need to verify and the doc needs to be updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
