Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry Dynamics
  3. Using a PKI Connector when UEM retrieves certificates for BlackBerry Dynamics apps
  4. PKI connector sample implementation
  5. Adapting the PKI connector sample implementation

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:
  • AdminServiceV9.wsdl
  • ServiceV9Common.xsd
These definitions are used to generate program stubs with Axis 1.4. Your CA might have similar definitions that you can use for your own adaptation of the PKI connector sample. You may also need to use a more recent version of Axis.
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