Hi Patrick,
Thanks for your reply.
I thought the "testAttribute_1" that I've before the NAME is consider as
OID, so I guess I cannot use letters to define OID?
> attributeTypes: ( *testAttribute_1* NAME
'testAttribute_1'
> ...
Is there some rule set that I must follow to define my OID? I noticed that
in "25java-object.ldif", the OID for javaClassName is "
1.3.6.1.4.1.42.2.27.4.1.6", so is it true that I must use numeric to define
my OID?
Regards,
David
On Nov 20, 2007 4:23 PM, Patrick Morris <patrick.morris(a)hp.com> wrote:
On Tue, 20 Nov 2007, Chun Tat David Chu wrote:
> Below is my schema
> dn: cn=schema
> objectClass: top
> objectClass: ldapSubentry
> objectClass: subschema
> cn: schema
> attributeTypes: ( testAttribute_1 NAME 'testAttribute_1'
> DESC 'This is testAttribute_1'
> EQUALITY caseIgnoreMatch
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.40
> SINGLE-VALUE
> X-ORIGIN 'user defined'
> )
> attributeTypes: ( testAttribute_1 NAME 'testAttribute_2'
> DESC 'This is testAttribute_2'
> EQUALITY caseIgnoreMatch
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.40
> MULTI-VALUE
> X-ORIGIN 'user defined'
> )
>
> Is the OID that I defined is invalid? If so what's the best way to
> generate a OID? or that's something wrong in my LDIF?
No, the problem is that you haven't defined an OID at all.
--
Fedora-directory-users mailing list
Fedora-directory-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users