encryptedAPKAMSymmetric key is missed when the pending enrollments are fetched.

[sitaram-kalluri]

Describe the bug:

• When a new app request for enrollment and the existing app receives the notification but doesn't take any action and goes offline.
• At this point, when the existing app is restarted and pending enrollments are fetched from the secondary server, the response contains "appName", "deviceName" and "namespaces". The response does not include "encryptedAPKAMSymmetricKey"

To approve an enrollment the encryptedAPKAMSymmetricKey is needed to encrypt the default encryption private key and default self encryption key and send them to server. But the enrollments that are fetched using "enroll:list" does not contain the encryptedAPKAMSymmetricKey.

Steps to reproduce

The enroll:list command does not have encryptedAPKAMSymmetricKey because of which pending enrollment cannot be approved by the approving apps.

Solution

Currently, the encryptedAPKAMSymmetricKey is not encapsulated in the EnrollDataStoreValue class which is used to store the enrollment params in the secondary server.

To fix the issue, include encryptedAPKAMSymmetricKey in the EnrollDataStoreValue and persist in the secondary server. When notify, fetch the value and notify along with the other enrollment params.

[sitaram-kalluri]

The changes are merged to trunk and release into canary in version 3.0.40a. Hence closing this git issue.