[KLUG Members] Pesky LDAP

[Eric Anderson]

*This message was transferred with a trial version of CommuniGate(tm) Pro*
I wouldn't think that adding to a schema to extend it would be a problem. If
the remote clients don't know that the data is in the directory, it really
shouldn't matter. You can also use the preexisting OID's to extend the schema
and define the syntax, depending on what you need.

Jim C (jcllings@tsunamicomm.net) wrote*:
>
>*This message was transferred with a trial version of CommuniGate(tm) Pro*
>> Schema extending should always be a last resort as you limit your
>> interoperability with various clients and the outside world.
>
>Are you saying that it is not a requirement?  I would rather avoid it if
>possible.
>
>>>Problem is that it reccomends makeing the following changes to the
>>>following files:
>...
>>>>'xmozillaanyphone' )
>>>Now what I've heard is that you should never edit the distributed
>>>schemas.
>> Correct.
>>>Rather you should create your own schema file and append it.
>>>Consequently, I made files with the appropriate changes and copied them
>...
>>>clases etc.
>
>Note: I did remember to exclude the old files but the changes I made
>were just as described.  Might it have been nescesary to adjust other
>settings in the same files to match the name additions?
>
>> You must have left something out on accident.  Which is pretty easy to
>> do.
>
>Well I'll try again this morning just in case but the changes were
>simple enough that I find that hard to believe unless the instructions
>themselves left something out.
>
>>>Now it seems to me that the simple addition of a name shouldn't affect
>>>other schemas in this manner.
>> No, it shouldn't.
>
>Could whitespace characters be the problem? Would it matter that I
>edited the files using MS Wordpad?
>
>>>Since it does seem to however, can't I
>>>just specify an alias in local.schema and then include local.schema in
>>>slapd.conf?  Can I get an example of how to do this?
>>
>>
>> It should be safe, if your just adding an alias, to edit the distributed
>> files.  Just keep a pristine copy somewhere.
>> However, the real solution is to fix the crud that is coming out of
>> Mozilla.  Mozilla's export format is psuedo-LDIF,  so as you massaged
>> the dn you may have to massage the attributes.
>> sed "s/xxmozillaanyphone/telephoneNumber/g" address.mozilla | sed
>> "s/pagerPhone/pager/g" | sed "s/cellPhone/mobile/g" > address.ldif
>
>I'll try this in a few.
>
>> should replace there attribute names with the legitimate one.
>
>Define legitamate? ;-)
>
>
>
>_______________________________________________
>Members mailing list
>Members@kalamazoolinux.org
>
>

--
Eric Anderson
LanRx Network Solutions
815-505-6132