Internal Attributes with user defined X-ORIGIN in DSEE 7?
807573Feb 2 2010 — edited Feb 17 2010Hello!
I am noticing DSEE 7 has some internal attributes listed as user defined in the schema:
attributetypes: ( 2.16.840.1.113730.3.1.605 NAME 'entryid' DESC 'Sun ONE defined attribute type' EQUALITY 2.5.13.2 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation X-ORIGIN ( 'Sun-Java(tm)-System-Directory/6.3.1' 'user defined' ) )
attributetypes: ( 2.16.840.1.113730.3.1.603 NAME 'dncomp' DESC 'Sun ONE defined attribute type' EQUALITY 2.5.13.1 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 NO-USER-MODIFICATION USAGE directoryOperation X-ORIGIN ( 'Sun-Java(tm)-System-Directory/6.3.1' 'user defined' ) )
attributetypes: ( 2.16.840.1.113730.3.1.604 NAME 'parentid' DESC 'Sun ONE defined attribute type' EQUALITY 2.5.13.2 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation X-ORIGIN ( 'Sun-Java(tm)-System-Directory/6.3.1' 'user defined' ) )
My customer wants to manage/archive their custom schema by scooping up 99user.ldif and submitting it into a file-based version tracking system (Perforce). However, since these internal DS attributes are now listed as user defined, they are going to hang around in 99user.ldif, making my customer feel dissatisfied and untidy. Actually, I see their point.
So, can I remove the X-ORIGIN of "user defined" on these and stick them in another schema LDIF? Are we planning on changing the schema definitions on these internal DS attributes in the future?