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
Is your feature request related to a problem? Please describe.
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.
There is no way for the client to fetch the enrollment information for the given enrollment Id.
Describe the solution you'd like
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.
Add "enroll:fetch" to retrieve the enrollment information for the given enrollment id.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
The text was updated successfully, but these errors were encountered: