directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "CORUM, M E [AG/1000]" <>
Subject RE: [ApacheDS] 1.5 Kerberos Support and Custom Attribute in Schema
Date Mon, 23 Apr 2007 22:00:26 GMT

Yes, thank you.  I had found that page earlier but had not read it yet.
The Kerberos stuff from the page that referenced it was inaccurate so I
wasn't sure whether these wiki pages were trustworthy or not.  I'll dig
into this more deeply.  Right now, I'm looking into the OIDs for Active
Directory's custom attributes (the over 200 additions to the standard
that AD makes).

Thanks again,


-----Original Message-----
From: Stefan Seelmann [] 
Sent: Monday, April 23, 2007 3:28 PM
Subject: Re: [ApacheDS] 1.5 Kerberos Support and Custom Attribute in

Hi Mike,

CORUM, M E [AG/1000] schrieb:
> [13:00:25] ERROR
> [] -
> Failed to import LDIF into backing store.
> rException: serviceprincipalname not found in attribute registry!
> 	at
> I assume I could add this attribute to the schema.  However, when I
> the custom schema stuff in the 1.0 documentation, it refers to a
> bootstrapSchemas section in the server.xml that doesn't exist.  I
> putting it in and the server won't come up so that doesn't work.  How
> this done now?  I assume it has changed but the change isn't
> Can anybody help with adding an attribute to the schema or set of
> schemas that ApacheDS uses?

The schema subsystem has totally changed with 1.5. Here you can find a
first (but good) draft of some documentation:

Stefan Seelmann

This e-mail message may contain privileged and/or confidential information, and is intended
to be received only by persons entitled to receive such information. If you have received
this e-mail in error, please notify the sender immediately. Please delete it and all attachments
from any servers, hard drives or any other media. Other use of this e-mail by you is strictly

All e-mails and attachments sent and received are subject to monitoring, reading and archival
by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence
of "Viruses" or other "Malware". Monsanto accepts no liability for any damage caused by any
such code transmitted by or accompanying this e-mail or any attachment.

View raw message