PI12365: CUSTOM DEVICE PROVISIONING WAS IMPLEMENTED, BUT WHEN DEPLOYING ON A REMOTE SERVER, IT DOES NOT WORK.

Download for IBM Worklight V6.1.0 Fix Pack 2
IBM Worklight Interim Fix README for 6.0.0.2

APAR status

• Closed as program error.

Error description

• We have built an app that uses Custom Device Provisioning
  according to the following document:
  http://public.dhe.ibm.com/software/mobile-solutions/worklight/do
  cs/v610/08_08_Custom_device_provisioning.pdf
  
  We had a working situation on the development environment, but
  when we moved the application to a remote server, the IOS app
  stopped working.  The android version works as expected. First
  the validateCSR function triggers, after that it moves on to
  the validateCertificate function.  However the iOS app does not
  trigger the validateCSR function anymore.  I tried removing the
  app and re-installing it, so it starts the provisioning process
  again, but that did not fix it.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Developers making use of device autoprovision or device      *
  * custom provisioning                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When provisioning, the client (ios, android) recieves and    *
  * stores a certificate to be used for signing whenever it      *
  * needs to answer the device provisioining challenge.          *
  * If that certificate changes, the application will not be     *
  * able to delete it and, in Android, the application (as well  *
  * as any other applications that have that same certificate    *
  * because of "group" or "device", provisioining granularity)   *
  * would need to be uninstalled.                                *
  * On iOS there is no way to recover from this condition.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• On both Android and iOS, for autoProvisioining the code has been
  modified to delete the certificate (if it is on the device),
  from all needed locations in case of receiving onFailure for the
  provisioining challenge, and thus the client can retry to answer
  the challenge to get the new certificate.
  
  If the developer chooses to use customDeviceProvisioining then
  he needs to add a call to
  challengehandlerName.clearDeviceProvisioningCertificate()
  method, preferably in the onFailure of the custom Challenge
  Handler.
  This method was added to the
  "createProvisioningChallengeHandler" method (which is used when
  the developer creates his own custom device provisioning
  handler)
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WORKLIGHT CONSU

• Fixed component ID

  5725I4301

Applicable component levels

• R600 PSY

     UP

• R610 PSY

     UP