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

fix: do not de-dup an 'enroll' request if the connection is CRAM-authenticated #2214

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

gkc
Copy link
Contributor

@gkc gkc commented Feb 4, 2025

- What I did
fix: do not reject duplicate 'enroll' requests if the connection is CRAM-authenticated. This matches legacy onboarding behaviour. Resolves #2208

- How I did it

  • Modified EnrollVerbHandler so that the duplicate check is skipped when the connection has been CRAM-authenticated
  • Added unit test
  • Renamed the duplicate-checking function for readability purposes

- How to verify it
Tests pass

…enticated. This matches legacy onboarding behaviour. Resolves #2208
@gkc gkc requested review from XavierChanth and cpswan February 4, 2025 01:27
@gkc gkc merged commit 8c7cafb into trunk Feb 4, 2025
26 checks passed
@gkc gkc deleted the fix-2208 branch February 4, 2025 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

atServer can be put into an unrecoverable state if the initial onboarding fails client side
2 participants