REGRESSION: JNDI example with SASL/GSSAPI does not work with J2SE 5.0

Name: jl125535 Date: 09/15/2004


URL OF FAULTY DOCUMENTATION :
http://java.sun.com/products/jndi/tutorial/ldap/security/gssapi.html

A DESCRIPTION OF THE PROBLEM :
The example works fine with J2SE 1.4, but with J2SE 5.0 the following exception is thrown:


javax.naming.NamingException: [LDAP: error code 80 - GSSAPI: gss_unwrap: A token had an invalid MIC; Success; ]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3029)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2931)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2732)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2646)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
at JndiAction.performJndiOperation(GssExample.java:144)
at JndiAction.run(GssExample.java:105)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:337)
at GssExample.main(GssExample.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:78)



I am using OpenLDAP 2.1.4 .

Release Regression From : 1.4.2
The above release value was the last known release where this
bug was known to work. Since then there has been a regression.

(Incident Review ID: 310807)
======================================================================