You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon app restarting, when the pending enrollments are fetched from the secondary server, the notification contains "appName", "deviceName" and "namespaces".
To approve an enrollment the encryptedAPKAMSymmetricKey is needed. 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.
The text was updated successfully, but these errors were encountered:
Describe the bug
Upon app restarting, when the pending enrollments are fetched from the secondary server, the notification contains "appName", "deviceName" and "namespaces".
To approve an enrollment the encryptedAPKAMSymmetricKey is needed. 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.
The text was updated successfully, but these errors were encountered: