UnboundID – My Shitty Code https://myshittycode.com Embracing the Messiness in Search of Epic Solutions Fri, 06 Jan 2023 16:29:15 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.1 https://myshittycode.com/wp-content/uploads/2022/04/cropped-icon-32x32.png UnboundID – My Shitty Code https://myshittycode.com 32 32 205304208 UnboundID: The entry contains attribute ‘XXXX’ which is not defined in the schema https://myshittycode.com/2017/03/28/unboundid-the-entry-contains-attribute-xxxx-which-is-not-defined-in-the-schema/ https://myshittycode.com/2017/03/28/unboundid-the-entry-contains-attribute-xxxx-which-is-not-defined-in-the-schema/#comments Wed, 29 Mar 2017 02:00:36 +0000 http://myshittycode.com/?p=931 PROBLEM Let’s assume we have the following LDIF file containing custom attribute(s), such as managedBy:- When running the code on UnboundID’s In-Memory Directory Server, the following exception is thrown:- SOLUTION The problem is caused by the fact that the default schema does not match Microsoft’s Active Directory schema. Hence, attribute(s), such as managedBy, would cause […]

The post UnboundID: The entry contains attribute ‘XXXX’ which is not defined in the schema appeared first on My Shitty Code.

]]> PROBLEM

Let’s assume we have the following LDIF file containing custom attribute(s), such as managedBy:-

dn: dc=MyShittyCode
objectClass: top
objectClass: domain
dc: MyShittyCode

dn: CN=ShittyEmployee,DC=MyShittyCode
objectclass: top
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
sn: ShittyEmployee
managedBy: CN=ShittyBoss,DC=MyShittyCode

When running the code on UnboundID’s In-Memory Directory Server, the following exception is thrown:-

LDAPException(resultCode=65 (object class violation),
errorMessage='Unable to add entry 'CN=ShittyEmployee,DC=MyShittyCode'
because it violates the provided schema:  The entry contains attribute
managedBy which is not defined in the schema.')
	at com.unboundid.ldap.listener.InMemoryRequestHandler.addEntry(InMemoryRequestHandler.java:4055)
	at com.unboundid.ldap.listener.InMemoryRequestHandler.importFromLDIF(InMemoryRequestHandler.java:3876)
	at com.unboundid.ldap.listener.InMemoryDirectoryServer.importFromLDIF(InMemoryDirectoryServer.java:1226)
	at com.unboundid.ldap.listener.InMemoryDirectoryServer.importFromLDIF(InMemoryDirectoryServer.java:1198)

SOLUTION

The problem is caused by the fact that the default schema does not match Microsoft’s Active Directory schema. Hence, attribute(s), such as managedBy, would cause an error.

While we can set a modified schema, which is very convoluted, the easiest solution is to completely disable the schema:-

def config = new InMemoryDirectoryServerConfig(base)
config.setListenerConfigs(new InMemoryListenerConfig("myListener", null, port, null, null, null))
config.setSchema(null)

def server = new InMemoryDirectoryServer(config)
server.startListening()
server.importFromLDIF(true, "target/test-classes/unboundid-test-data.ldif")

The post UnboundID: The entry contains attribute ‘XXXX’ which is not defined in the schema appeared first on My Shitty Code.

]]> https://myshittycode.com/2017/03/28/unboundid-the-entry-contains-attribute-xxxx-which-is-not-defined-in-the-schema/feed/ 1 931