KMIP Interoperability Testing

OASIS KMIP Interoperability Testing

The OASIS KMIP Technical Committee performs interoperability testing between vendor implementations prior to the annual RSA Conference OASIS KMIP demonstration or in separate events.

Prior to each conference event, a couple of weeks of intensive testing is performed between the vendors participating in the OASIS KMIP vendor booth to confirm that all vendor products are able to perform at least one test between any two given product pairs (where each product pair is a KMIP client combined with a KMIP server).

After the testing completes, the Interop Team Lead collates the results and the vendors perform cross-validation of the results. When all disputed results have been resolved and the results formally approved by the vendor participants, the Interop Team Lead prepares a summary report for the KMIP technical committee which is published prior to the commencement of the RSA Conference.

The KMIP specification uses test cases in two contexts - one to demonstrate specification capability (contained in the Test Cases documents) and the other for formal conformance testing (contained in the Profile documents). The KMIP Profiles are a mandatory part of the KMIP Specification and in order to claim conformance to the specification, a vendor has to pass the mandated test cases against the profiles.

Profile Test Cases are defined for all versions of the KMIP specification and are within the scope of the interop testing.

Each interop test covers the current version of the KMIP specification and the in-development version. Superseded versions are no longer included.

By KMIP TC standing rule, formal Statements of Use are only accepted from vendors who have successfully participated in a KMIP interop test. Three statements of use are required for an OASIS standard to be accepted for approval.