We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Without this safeguard, a revoked app could remain connected until the network connection is lost or the server is restarted etc
When an enrollment is revoked, any clients connected via that enrollment should be immediately disconnected
No response
The text was updated successfully, but these errors were encountered:
@gkc If a client submits enroll:revoke for self with force flag, should we drop the client connection on the server?
Sorry, something went wrong.
@murali-shris Yes please. Ideally sending a response first so the client knows the revocation was successful and connection will be closed
murali-shris
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
Without this safeguard, a revoked app could remain connected until the network connection is lost or the server is restarted etc
Describe the solution you'd like
When an enrollment is revoked, any clients connected via that enrollment should be immediately disconnected
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: