Extending Samba4 schema

[Anatoliy Atanasov]

Hi, 

Can you try to add oMObjectClass: \x2b\x0c\x02\x87\x73\x1c\x00\x85\x4a
after oMSyntax: 127
This is applicable to objects with attributeSyntax: 2.5.5.1
This should fix the error and the resolving of the syntax.

Regards, Anatoliy
----- Original Message -----
> From: "samba-technical-bounces at lists.samba.org" <samba-technical-bounces at lists.samba.org> on behalf of "Adam Tauno Williams" <awilliam at whitemice.org>
> To: "samba-technical at lists.samba.org" <samba-technical at lists.samba.org>
> Cc: 
> Sent: Monday, December 6, 2010 5:11:10 PM (GMT+02:00) Athens, Bucharest, Istanbul
> Subject: Re: Extending Samba4 schema

> > On Mon, 2010-12-06 at 10:07 -0500, Adam Tauno Williams wrote: 
> > On Sun, 2010-12-05 at 03:16 +0000, Andris Lismanis wrote: 
> > > Following on from
> > > 
> 'http://lists.samba.org/archive/samba-technical/2010-November/074786.ht
> ml' thread, I have come across another problem. I have been playing 
> with Samba4 and Zarafa integration. I have managed to extend most of 
> attributes with exception of few. Samba4 ldb seems to crash when 
> importing the following type of attribute: 
> > > dn: CN=Zarafa-Send-As,<SchemaContainerDN>
> > > changetype: add
> > > adminDisplayName: Zarafa-Send-As
> > > attributeID: 1.3.6.1.4.1.26278.1.1.2.4
> > > attributeSyntax: 2.5.5.1
> > > cn: Zarafa-Send-As
> > > distinguishedName: CN=Zarafa-Send-As,<SchemaContainerDN>
> > > instanceType: 4
> > > isSingleValued: FALSE
> > > lDAPDisplayName: zarafaSendAsPrivilege
> > > name: Zarafa-Send-As
> > > objectCategory: CN=Attribute-Schema,<SchemaContainerDN>
> > > objectClass: top
> > > objectClass: attributeSchema
> > > oMSyntax: 127
> > > schemaIDGUID:: xpDaV2kqTtOVsFJD/YqQuw== 
> > > showInAdvancedViewOnly: TRUE
> > > searchFlags: 0
> > > It looks like samba does not like either oMSyntax: 127 (other 
> syntaxes
> > > are fine) or attributeSyntax: 2.5.5.1 (other attributes are fine). 
> I
> > > have tested this both on 4.0.0alpha12-GIT-f12756b
> > > and 4.0.0alpha14-GIT-929063b
> > > Can someone confirm that this is to do with full AD schema issue 
> or is
> > > this something else and whether there is any way round this.
> > > I'm also attaching the original LDF file that comes with Zarafa.
> > > Please note that changetype has been changed to add and
> > > <SchemaContainerDN> to CN=Schema,CN=Configuration,DC=example,
> DC=com
> > I believe there is some kind of issue regarding creating attributes 
> with
> > the 2.5.5.1;  even if you can create them they don't appear to be
> > usable.  I was able to import a scheme definition for 
> radiusProfileDn -
> > dn:
> > CN=Radius-Profile-DN,CN=Schema,CN=Configuration,DC=AD,DC=MORMAIL,
> DC=COM
> > objectClass: top
> > objectClass: attributeSchema
> > attributeID: 1.3.6.1.4.1.3317.4.3.1.49
> > schemaIdGuid:: 73QFH4g40KDiaTjSuh90WQ==
> > cn: Radius-Profile-DN
> > name: radiusProfileDn
> > lDAPDisplayName: radiusProfileDn
> > attributeSyntax: 2.5.5.1
> > oMSyntax: 127
> > isSingleValued: TRUE
> > but in the "Active Directory Schema" snap-ip the syntax for this
> > attribute appears as "Unknown".
> 
> And once loaded the samba.log file fills with a steady series of:
> 
> [Mon Dec  6 10:08:05 2010 EST,
> 0 ../dsdb/schema/schema_init.c:686:dsdb_attribute_from_ldb()]
> ../dsdb/schema/schema_init.c:686: Unknown schema syntax for
> radiusProfileDn
> [Mon Dec  6 10:08:05 2010 EST,
> 0 ../dsdb/schema/schema_init.c:829:dsdb_schema_from_ldb_results()]
> ../dsdb/schema/schema_init.c:829: schema_fsmo_init: failed to load
> attribute definition:
> CN=Radius-Profile-DN,CN=Schema,CN=Configuration,DC=ad,DC=mormail,
> DC=com:WERR_DS_ATT_SCHEMA_REQ_SYNTAX
> 
> 4.0.0alpha14-GIT-03b078c