Insufficient access error

When replication returns an insufficient access error, the reason might be related to the version of IBM® Verify Directory on the consumer. Follow the steps to troubleshoot and work around this problem.

Consider a scenario where a replication topology extended operation is issued to a server that is of IBM Verify Directory, version 6.0 or later. However, if the consumer of the server has a release earlier than version 6.0, the operation fails. In the server trace, you can identify insufficient access as the cause of the failure.

When a replication topology extended operation is issued to a server, the server propagates all of its replication topology entries to its consumers. However, the consumers must be of version 6.0 and later. For a consumer that has a release earlier than version 6.0 to have the same replication topology entries as its supplier, import and export tools, such as idsdb2ldif and idsldif2db, can be used.