Re: ANS1 ID questions
Edward van der Maas
>
> We have an official ANS1 ID from Novell. And we extended the schema
> with multiple attributes using this same ANS1 ID.
>
> When I browse the tree with apache studio I see that apache doesn't
> know how to handle multiple attributes with the same ANS1 ID.
> ConsoleOne, on the other hand, has no problems with it.
>
> I have a few questions:
> - Is the ANS1 ID of an attribute suppose to be unique in one tree? Or
> can I leave it this way?
Each ASN1 ID is per attribute I believe.
> - What is the use of even having a registerd ANS ID?
Well, you can then claim that myUniqueAttributeName has ASN1 ID of
1.2.3.4.x.x. I've never really used it at customer and I've done
numerous schema extensions with custom attributes.
--
Cheers,
Edward
a...@novell.com
Hash: SHA1
This document is a little helpful with identifying stuff along these lines.
http://support.novell.com/techcenter/articles/dnd19991102.html
My understanding is that if you have the ASN.1 from Novell for your
registered schema prefix then you get a certain set of numbers... for example:
2.16.840.1.113719 (for Novell)
and then off of that you define classes, attributes, syntaxes, etc. so
that you control the unique definition for each attribute you define:
2.16.840.1.113719.1.14.4.1.2479
If you are using the same one for everything then anything relying on that
being unique per attribute or class will be unhappy, but some other tools
that do not rely on that will be less-caring.
I believe you can change schema via LDAP by removing and adding back the
attribute (changed when adding back) in the same operation as long as it
is not a change that impacts objects in the tree (this probably isn't).
As an example that I have not tested at all:
dn: cn=schema
changetype: modify
delete: attributeTypes
attributeTypes: ( 1.3.6.1.1.1.1.2345 NAME 'bootParameter' DESC
'rpc.bootparamd parameter' SYNTAX 1.3.6.1.4.1.1466.115.121.1.40{64512}
X-NDS_NAME 'bootParameter' )
- -
add: attributeTypes
attributeTypes: ( 1.3.6.1.1.1.1.23456 NAME 'bootParameter' DESC
'rpc.bootparamd parameter' SYNTAX 1.3.6.1.4.1.1466.115.121.1.40{64512}
X-NDS_NAME 'bootParameter' )
So all that I did was take the old one and change the number at the
beginning. This is all one "operation" because it is all on the same
object and has a '-' separating the delete and add attribute operations on
that same object.
Good luck.
eddy wrote:
> Is there any way to change the ANS1 Id of an attribute without removing
> the attribute from the schema?
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJLKlATAAoJEF+XTK08PnB5UJwP/01078Hi4B2FI7mTjTr/6CxY
4mIgFVut2sq3TV0qBq79QdH95xIlq2S+DlpCJqgWxh/l4fPz6ZZw+zFDHaL6pB+t
vfxO6VPOKuhjK1tSs/gHa+sFdGOkYIAALwEK/B21wxzTKNTV+fP+PWp+bJY15urz
MFukI3CXwBVP6+/mDg8+hJ7X+7nEg894+f110vRfAkjS+GEt2JOml6cPRjwsInuE
2nyYaTlaKJCgq34AKg19b3Yirt/PVbxbliWCqSAUB6W61shiWc1qc32byqrlxruw
fI4CnPqjQbnfF47X4pHHM/Wo0eA8PY4zRPOyPrh+4xg5Z/i6rzUYjcWRL5vjSztW
luVuoj9b5J2M7iWh1qTw4LXWzuReOYQrEgfX5mRbtQnG+qYEXVobtkCe7c9IqiBF
Na+OSWKDM1VYMa4aKYNDND7Lkk8wojiYdohqdoCxx7w8yNbgQBJvrj2Ov8F+24cg
t4DBrCyOprd8gWtrkiJNC4x+5l85xZ4C/rvxw16xY9ZRCsYXL6Dng4tnw+qOLlSQ
+aMbsveN3MKZqCEr0nki7fOme1CqsTMJXZNi5FuMHDY7BY7YMp7MGS/8N37S+nm2
CwQF/D1kMziMT1jAhejE3YwmU0Sgus768R798zVYfTXE0+RxCBTynVt3jv3tmkMQ
hh9t8k1LTbfdVQ3KzWLA
=0ZtH
-----END PGP SIGNATURE-----