bnelson.com Home Page



















Fool your friends! Frustrate your Boss! Wipe out a client! Here are some fun things to try on your product that don't necessarily work as advertised.

By the way, if/when I ever find answers to these questions, I will post them here as well.

If you find some "anomolies" of your own, go ahead and send them to me here. I will post them for you and give you full credit (unless you don't want your boss to know what problems lurk in the products you support). Please provide which product you are using (please stay within the realm of products listed on this site, i.e. directory servers), the version you are using, the version of the OS, and the steps you took to recreate it. Send this information to: bill.nelson@gmail.com.


Netscape Directory Server

    Replication - Extended Schema is "Magically" Replicated

    Overview: Netscape says that extended schema items (objects classes/attributes) will not be replicated unless the consumer schema has also been extended. This is not the case.

    Platform: Netscape Directory Server v4.1 on Solaris 2.7

    Steps to Recreate Anomoly:

    1. Create replication agreement between a Supplier and a Consumer.

    2. Create user on Supplier server (verify it also was created on consumer server) => call this user jkirk (why? because the old Star Trek was better!)

    3. Extend schema on Supplier server. Add new attribute (bnelsonHairColor) and new Object Class containing that attribute (bnelsonOrgPerson - superior = inetOrgPerson).

    4. Add new object class to jkirk and go ahead and add a value to that new attribute.

    5. Look at jkirk on the consumer server and you will see he has the new object class and attribute with the same values as the supplier server.

    Sanity Check:

    1. Verify that the schema was not "actually" extended on the consumer server. You can do this via the Netscape Console by looking at the schema itself, by looking at the $NSHOME/slapd-hostname/config/slapd.user_at.conf and $NSHOME/slapd-hostname/config/slapd.user_oc.conf and verifying they do not contain the new definitions, or by simply doing an LDAP search on your Communicator browser (ldap://hostname:port/cn=schema) and verifying that it is not there.

    2. Oh yes, verify that Schema Checking is on in the Consumer Server.

      So how does it get there? Well, it's a mystery!