Adapting the PKI connector sample implementation
Note the following considerations when you modify the PKI connector sample implementation to work with a CA other than
Entrust
:Item | Consideration |
---|---|
Start with CertificateServerService.Java | CertificateServerService.java (in src/main/java/com/good/service/) indicates the various touch points that you need to account for when you set up your own PKI connector. |
Adhere to the BlackBerry Dynamics User Certificate Management Protocol | You must ensure that any adaption of the sample implementation also implements the standards and processes of the BlackBerry Dynamics User Certificate Management Protocol. |
Generating program stubs | The sample implementation relies on the following Entrust files that are included with the software:
|
Property handling | You will need to set up a properties file similar to entrustMdmWs.properties for your intended CA. |
Format of certificate data | The sample implementation receives a byte stream of the unencoded certificate data from Entrust . The format of the certificate depends on your intended CA. You may need to modify your implementation to process data in a different format |