@Override
  protected final void postSetUpClientAuthorizationTestBase() throws Exception {
    // required by FilterPreAuthorization and FilterPostAuthorization. Normally,
    // this would be automatically registered in the static initializer, but with dunit
    // a previous test may have already loaded these classes. We clear the instantiators
    // between each test.
    server1.invoke("registerInstantiator",
        () -> Instantiator.register(new MyInstantiator(), false));
    server2.invoke("registerInstantiator",
        () -> Instantiator.register(new MyInstantiator(), false));
  }
Tests for authorization callback that modify objects and callbacks from client to server.

The scheme of these tests is thus: A user name terminating in integer 'i' can get values
terminating with 'i', '2*i', '3*i' and so on. So 'gemfire1' can get 'value1', 'value2', ...;
'gemfire2' can get 'value2', 'value4', ... and so on. On the server side this is done by adding
the index 'i' to the object in the pre-processing phase, and checked by comparing against the
user name index during the post-processing phase.

This enables testing of object and callback modification both in pre-processing and
post-processing phases.

@since GemFire 5.5
geode-cq/src/distributedTest/java/org/apache/geode/security/ClientAuthzObjectModDUnitTest.java