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

When an enrollment is revoked, any clients connected via that enrollment should be immediately disconnected #1927

Closed
gkc opened this issue Apr 28, 2024 · 2 comments · Fixed by #1939
Assignees
Labels
enhancement New feature or request

Comments

@gkc
Copy link
Contributor

gkc commented Apr 28, 2024

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

@gkc gkc added the enhancement New feature or request label Apr 28, 2024
@murali-shris
Copy link
Member

@gkc
If a client submits enroll:revoke for self with force flag, should we drop the client connection on the server?

@gkc
Copy link
Contributor Author

gkc commented May 2, 2024

@murali-shris Yes please. Ideally sending a response first so the client knows the revocation was successful and connection will be closed

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