| |
NoSuchAttributeException: Alias of Attribute Type Not Found |
|
|
Subject: NoSuchAttributeException: Alias of Attribute Type Not Found
Author: eLDAP
In response to: javax.naming.InvalidNameException: Unknown Attribute Value Used in RDN
Posted on: 08/10/2006 04:22:09 AM
++++++++++++++++++++++++++++++++++
+
+ Test Run #6: Alias of Attribute Type
+
++++++++++++++++++++++++++++++++++
dn: cn=Joe Smith,cn=users,dc=mydomain,dc=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgperson
cn: Joe Smith
surName: Smith
givenname: Joe
mail: bsmith@mydomain.com
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3009)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2934)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2740)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:777)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:176)
-- Results From SunOne --OK with the following value being added instead:
sn: Smith
WhyThe entry's attribute type 'surName' is neither defined in the MUST list nor in the MAY list of its all object classes. That's why AD forbids it being added. But SunOne seems to be much smarter by figuring out that 'surName' is actually the alias of 'sn' and going one step further by transferring 'surName' to 'sn' while adding it.
>
> On 08/10/2006 04:04:06 AM eLDAP wrote:
++++++++++++++++++++++++++++++++++
+
+ Test Run #5: Unknown Attribute Value Used in RDN
+
++++++++++++++++++++++++++++++++++
dn: cn=Joe Smith,cn=users,dc=mydomain,dc=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgperson
cn: Joe_Smith
sn: Smith
givenname: Joe
mail: bsmith@mydomain.com
-- Results From AD --
javax.naming.InvalidNameException: cn=Joe Smith,cn=users,dc=mydomain,dc=com: [LDAP: error code 34 - 00002081: NameErr: DSID-03050AE0, problem 2003 (BAD_ATT_SYNTAX), data 0, best match of:
'cn=Joe Smith,cn=users,dc=mydomain,dc=com'
remaining name 'cn=Joe Smith,cn=users,dc=mydomain,dc=com'
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2926)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2740)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:777)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:176)
-- Results From SunOne --
OK with the following extra value being added:
cn: Joe Smith
Why
The value 'Joe Smith' used in RDN does not match what goes with 'cn', i.e. 'Joe_Smith'. That's why AD forbid it being added. But SunOne let it go through with 'Joe Smith' being automatically inserted as another value of 'cn'.
References:
|
|
|
|
