[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Extending schema
- To: <openldap-software@OpenLDAP.org>
- Subject: RE: Extending schema
- From: "Garzon Maldonado, Jesus Javier" <jgarzon@indra.es>
- Date: Thu, 3 Jul 2003 18:01:42 +0200
- Content-class: urn:content-classes:message
- Thread-index: AcNBct3UNZWJGyaqSe6PxAvQDZOIAwACIUkA
- Thread-topic: Extending schema
I've already done this. However, when I launch slapd a syntax not found error appear:
acp133.schema: line 532: Syntax not found: "2.16.840.1.101.2.2.2.17"
This attribute syntax is:
[I don't know what should be here] (2.16.840.1.101.2.2.2.17
NAME aCPLegacyFormat
DESC 'aCPLegacyFormat syntax')
# The encoding of a value in this syntax is any one of the INTEGER
# values: 0 - 15 or 32 - 48 where:
# 0 means JANAP128,
# 1 means ACP126,
# 2 means DOI103,
# 3 means DOI103Special,
# 4 means ACP127,
# 5 means ACP127Converted,
# (6 means Reserved1),
# 7 means ACP127State,
[...]
The same happens with name forms, content rules and matching rules.
I haven't found any example of how these items are defined.
Regards.
> -----Mensaje original-----
> De: Chris Brook [mailto:cbrook@v-one.com]
> Enviado el: jueves, 03 de julio de 2003 16:54
> Para: Garzon Maldonado, Jesus Javier; openldap-software@OpenLDAP.org
> Asunto: RE: Extending schema
>
>
> Create your own schema file, e.g. acp133.schema, with all the
> attributes and object classes that you need, put it in
> /usr/local/etc/openldap/schema and add a line to
> /usr/local/etc/slapd.conf:
> include /usr/local/etc/openldap/schema/acp133.schema
> Chris Brook
>
> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Garzon
> Maldonado, Jesus Javier
> Sent: Thursday, July 03, 2003 8:35 AM
> To: openldap-software@OpenLDAP.org
> Subject: Extending schema
>
>
> Hello all:
>
> I'm using OpenLDAP 2.0.35 on FreeBSD 4.7.
>
> I wish to include ACP 133 specification wich includes new
> objects, and attribute definitions together with new name
> forms, syntax and content rules definitions.
>
> However, I don't know how or where attribute syntaxes,
> content rules and name forms are defined. Does anybody know?.
>
> I just know some basic concepts like how to add new objects
> and attributes. :o(
>
> ACP 133 states things like:
>
> [...]
> 4. NAME FORMS
>
> 4.1 aCPNetworkEdBNameForm
>
> ( 2.16.840.1.101.2.2.4.42 NAME 'aCPNetworkEdBNameForm'
> OC 2.16.840.1.101.2.2.3.68 ; aCPNetworkEdB
> MUST 2.5.4.3 ) ; cn
> [...]
>
> 5. MATCHING RULES
>
> 5.1 addressCapabilitiesMatch Matching Rule
>
> ( 2.6.5.4.1 NAME 'addressCapabilitiesMatch'
> SYNTAX 2.16.840.1.101.2.2.2.16 ) ; Address
> Capabilities syntax
>
> [...]
>
> 6. ATTRIBUTE SYNTAXES
>
> 6.1 aCPLegacyFormat Attribute Syntax
>
> ( 2.16.840.1.101.2.2.2.17 DESC 'aCPLegacyFormat syntax' )
>
> The encoding of a value in this syntax is any one of the INTEGER
> values: 0 - 15 or 32 - 48 where:
>
> 0 means JANAP128,
> 1 means ACP126,
> 2 means DOI103,
> 3 means DOI103Special,
> [...]
>
> 7. EXAMPLE CONTENT RULES
>
> The content rules given in ACP 133(B) [1] are examples, not
> requirements. The rules included in this document are examples
> to aid in the specification of similar content rules, especially
> those derived from these examples.
>
> 7.1 aCPApplicationEntityRuleEdA Content Rule
>
> ( 2.5.6.12 NAME 'aCPApplicationEntityRuleEdA'
> ; applicationEntity object class
> AUX ( 2.5.6.22 $ ; pkiCA
> 2.16.840.1.101.2.2.3.66 ) ; securePkiUser
> MAY ( 2.16.840.1.101.2.2.1.49 $ ; aliasPointer
> 2.5.4.46 $ ; dnQualifier
> 2.16.840.1.101.2.2.1.55 $ ; effectiveDate
> 2.16.840.1.101.2.2.1.57 ) ) ; expirationDate
>
> [...]
>
> .... and I don't know what should I do.
> Any help will be appreciated.
> Regards.
>
> Javi Garzon.
>
>