Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Info
titleLast Certificate Rollover Date is Upcoming - was November 12, 2013

Notice: CommCare's last security certificate renewal date
is approaching
was on November 12, 2013. This means that
on that date
after November 12, 2013, Nokia phones will not allow you to install a copy of CommCare that was created before September 26, 2013, when the new certificate entered service.

What do I need to do?
If you are managing a deployment, all you need to do is go to the "Deploy" section and make a new version of each of your applications. Any time a new installation is performed, it should be done with a version that has been made since September 26, 2013. You may need to make and save a small change to enable making a new version.

Some commonly asked questions are answered below, followed by technical details about application signing

FAQ's

Q. Which projects are affected by the rollover?

All Java Phone projects which have versions built and in use from before September 26, 2013, when the new certificate was introduced. Android Projects are not affected by the certificate rollover.

Q. Will my versions currently installed and in use on phones keep working after the rollover date (November 12)? 

...

Yes. Applications which were "installed" (run at least once) before the certificate rollover will continue working on their current phone with no intervention. The only exception is if an application is being run directly from an SD Card, and the SD card is removed

Q. How will I know if my CommCare mobile users are having a problem with their certificate?

...

and re-inserted. In this case the phone will re-validate the certificate.

Q. How do I update an application to be signed against a new certificate?

On CommCare HQ, applications are signed each time a new build version is made. If you make a new build version after the certificate has entered service (September 26, 2013), it will be signed with the new certificate. If no other changes have been made you should simply be able to install "over" the original applicaiton, retaining the installed files. .

Q. How will I know if my CommCare mobile users are having a problem with their certificate?

Upon opening CommCare, a mobile user would see the message: "Certificate invalid according to phone's date."

Q. Is there any way to install an old version if I really need to?


Yes. If the phone gives you the error "Certificate invalid according to phone's date" you when you try to run CommCare, you can still run that version. There are two workarounds for running a version of CommCare which has an expired certificate

Workaround

1

- Change the phone's time

(recommended)

  1. On the phone, go to the settings menu, and configure the phone's date and time settings. Set the date to be inside the validity period for the certificate used to sign the binary you are running (from the table above)before the certificate expired.
  2. Run CommCare at least once, being sure to set any of the necessary application access permissions beforehand
  3. Return to the settings menu and set the phone's date and time to the correct value

Q. Do I need to update which version of CommCare my

...

application is built

...

with (IE: CommCare 2.3.0 to CommCare 2.8.0) in order to get the new certificate?

No. The application is signed after the buildversion is created, and CommCare retains the binary for all of the prior versions which have been built against, so you can make a new build of your app with its current CommCare version, regardless of which version of CommCare you are running. However, we do recommend that you consider updating CommCare if you are getting a new certificate in order to take advantage of new bug fixes and features available on newer versions of CommCare.

...

Service Entry

Certificate Valid From

Certificate Expiration Date

Status

 

November 2, 2009

November 13, 2010

Expired

 

September 21, 2010

November 13, 2011

Expired

November 14, 2011

September 13, 2011

November 12, 2013

Valid (retired)Expired

September 26, 2013September 24, 2011November 12, 2015Valid

...