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

Add validation to prevent duplicate enrollment with existing appName and deviceName #1923

Closed
sitaram-kalluri opened this issue Apr 26, 2024 · 0 comments · Fixed by #1920
Closed
Assignees
Labels
enhancement New feature or request

Comments

@sitaram-kalluri
Copy link
Member

sitaram-kalluri commented Apr 26, 2024

Is your feature request related to a problem? Please describe.

  1. Currently, the secondary server lacks specific checks when processing new enrollments. It does not prevent new enrollments that share the same appName and deviceName with an existing one if the exisiting enrollment is in either an "approved" or "pending" state.
  2. There is no way for the client to fetch the enrollment information for the given enrollment Id.

Describe the solution you'd like

  1. When submitting a new enrollment, add validations on the server side, to throw an exception if an enrollment with the same appName and deviceName with the existing enrollment if the existing enrollment is either an approved or pending state.
  2. Add "enroll:fetch" to retrieve the enrollment information for the given enrollment id.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants