Repository navigation
Fix service-link consent recovery and bounded protocol token reuse - #131
Merged
Merged
Conversation
This was referenced Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background workers were writing scheduling updates to attempts still awaiting administrator consent, creating avoidable approval conflicts. Protocol recovery also acquired a new token for each retry. Keep live consent waits unchanged and reuse verification/control tokens for the exact current peer, tenant, scope and credential revision.
Every use rechecks durable authority and current endpoint policy. Expiry, terminal recovery permissions, rotation journals, rate limits and timeouts retain their existing bounds. Prepare RatelDesk 0.1.1-beta.13 through the central version properties and record the corrections in the release notes.
Validation: