Re: [ldapext] Dynamic values in LDIF

[Michael Ströder <michael@stroeder.com>]

Jim Sermersheim wrote:
>  >>>> Michael Ströder <michael@stroeder.com> 11/8/04 3:15:25 AM >>>
>  >Jim Sermersheim wrote:
>  >>
>  >> It's difficult (well, impossible I guess) to write an LDIF file which
>  >> can be used to update schema because one never knows the name of the
>  >> subschema subentry in effect for the object(s) for which the schema
>  >> is being updated. (I'm assuming a DSA which can modify schema. i.e.
>  >> X.501(93) Clause 14.5).
>  >
>  >There's not a single sub schema sub entry. In fact there could be many.
>  >=> you have to know something a priory about the DSA before updating one
>  >of its sub schema sub entries.
> Exactly (thus the "in effect for the object(s)" bit). This is why I'm 
> wondering about a mechanism to (apriori) gather the knowledge needed to 
> update the schema which the application intends to update.

Kind of a mind-reading machine? ;-)

Well, if someone would like to implement a generic sub schema modifying 
program this would need as input params to modify a certain sub schema 
at least:
- machine (host:port)
- naming context
- authentication credentials
- some connection-oriented stuff (e.g. LDAPS to a separate port)

Frankly I have no clue how these params could be guessed. They are given 
at run-time by an admin who simply knows them. Now if you invoke a 
program with params you can't guess you can easily implement all your 
sub schema modifications in that program.

> I apparently worded my message poorly. My intent is to NOT have to 
> implement anything other than an LDIF file.

I can imagine quite well what you want. IMO it's simply not possible 
without some program interpreting the LDIF data within some context 
known a priori.

Ciao, Michael.


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext