Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

inconsistent formats in server response for enrollment:list vs enrollment:fetch #1928

Closed
gkc opened this issue Apr 28, 2024 · 0 comments · Fixed by #1929
Closed

inconsistent formats in server response for enrollment:list vs enrollment:fetch #1928

gkc opened this issue Apr 28, 2024 · 0 comments · Fixed by #1929
Assignees
Labels
bug Something isn't working

Comments

@gkc
Copy link
Contributor

gkc commented Apr 28, 2024

Describe the bug

enroll:fetch and enroll:list return different JSON structure the same enrollmentId

Steps to reproduce

In a response from enroll:list, the enrollment looks like this

"f02825db-afb0-4726-8459-5adce1e267ee.new.enrollments.__manage@alice":{
  "appName":"test",
  "deviceName":"dev1",
  "namespace":{"buzz":"rw"},
  "encryptedAPKAMSymmetricKey":"[....]",
  "status":"revoked"
}

The same enrollment looks like this from enroll:fetch

{
  "sessionId":"_ca2bc326-d6e1-48af-8af3-e1c2cd818177",
  "appName":"test",
  "deviceName":"dev1",
  "namespaces":{"buzz":"rw"},
  "apkamPublicKey":"[...]",
  "requestType":"newEnrollment",
  "approval":{"state":"revoked"},
  "encryptedAPKAMSymmetricKey":"[...]"
}

Expected behavior

Basic structure should be the same. Note in particular

  • namespace vs namespaces
  • status vs approval
@gkc gkc added the bug Something isn't working label Apr 28, 2024
@gkc gkc closed this as completed in #1929 Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
2 participants