CM-72432: Retry token mint when a concurrent login is refused - #546
Merged
Merged
Conversation
![cycode-security[bot]](https://avatars.githubusercontent.com/in/39308?s=60&v=4){kind=small}
AI guardrails runs one CLI process per hook, and every process shares one cached token with a single expiry stamp, so a burst of them mints at the same instant. The identity provider's brute-force protection refuses same-user logins that land within milliseconds of each other, so all but the first are rejected. The refused scans fail open and record a scan failure, leaving the interaction unscanned. On a 401 during refresh, wait briefly and prefer the token the winning process has just persisted, minting again only if nobody won. The wait is randomized so the refused processes do not collide a second time. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Ilanlido
force-pushed
the
CM-72432-retry-token-mint-on-auth-conflict
branch
from
September 14, 2026 17:47
4cd809b to
b439bf0
Compare
Ilanlido
enabled auto-merge (squash)
September 15, 2026 11:09
omer-roth
reviewed
Sep 15, 2026
omer-roth
approved these changes
Sep 15, 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
2 participants
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.
AI guardrails runs one CLI process per hook, and every process shares one cached token with a single expiry stamp, so a burst of them mints at the same instant. The identity provider's brute-force protection refuses same-user logins that land within milliseconds of each other, so all but the first are rejected. The refused scans fail open and record a scan failure, leaving the interaction unscanned.
On a 401 during refresh, wait briefly and prefer the token the winning process has just persisted, minting again only if nobody won. The wait is randomized so the refused processes do not collide a second time.