Uploaded image for project: 'Z-Push'
  1. Z-Push
  2. ZP-1151

Ping fails with Provisioning required after policy key update

    Details

    • Type: Bug
    • Status: QA
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 2.3.4
    • Fix Version/s: 2.3.5beta1, 2.3.5
    • Component/s: None
    • Labels:
      None

      Description

      An Asus android device decided to do a Provisioning request randomly.
      This triggers a series of events as follows:

      • triggers a Provisioning request
      • a new key is deployed
      • In the following request the device syncs the hierarchy and the new key is correctly validated. There are no changes, fd is not updated.
      • Several Sync requests happen, but no changes are found. Folderdata is not updated.
      • device does a Ping request:
      1. Ping itself the device does not send a provisioning key as in the standard sync requests.
      2. To still be able to detect changes, we take the so called reference policy key from the metadata of each folder and consider the last one.
      3. The keys mismatch (old reference policy key mismatches new key)
      4. Ping returns status 7 to force a FolderSync

      A solution should be to force the update of the folderdata in case the provisioning keys of the metadata doesn't match the one sent from the device.

      Reported in the forums: https://forums.zarafa.com/showthread.php?13271-Z-Push-2-3-5b0-ProvisioningRequiredException-breaks-sync

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Sebastian Sebastian Kummer
                Reporter:
                Sebastian Sebastian Kummer
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: