Repository navigation
Conversation
⏱ Benchmark Resultsbenchstat comparison (baseline → PR)
|
This was referenced Oct 9, 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.
Managed agent grants need a signing boundary that preserves their approved subject, tenant, grant version, audience, scopes and expiry. This adds a typed
M2MAuthModule.IssueManagedTokenAPI with fixed protected claims, explicit stable ES256 configuration, an internally generated JTI and a 15-minute lifetime cap. Managed JWT and JWKS key IDs use the existing RFC 7638 thumbprint helper.The dedicated issuer must opt into
SetManagedOnly(true), which denies generic token, revoke and introspection handlers before parsing inputs. JWKS remains readable and the default legacy issuer, expiry, provider and revocation behavior remain compatible. The API is reusable for any approved positive tenant/grant version and exact HTTPS audience; it contains no deployment-specific identities.The reusable auth integration separately owns approved grants, current policy/version/expiry/revocation checks, exchange replay protection, strict JWT authorization and audit. This PR does not enable a managed identity or endpoint, create credentials or keys, update dependency pins, release or deploy a service.
Validation at frozen head
9971ca5067f3b6a7cafe9667e381efab62e52d1c, based on current mainf043410f5dc727af7adc800e48786a31c09b3f7e:GOWORK=off GOPROXY=off GOTOOLCHAIN=local GOFLAGS=-mod=readonly GOMAXPROCS=2 go test -race -p 2 -count=1 -v module/auth_m2m.go module/auth_m2m_managed.go module/auth_m2m_managed_test.go.git diff --checkpassed. Full module builds/tests were not run locally; existing repository CI and independent review remain required before any release.The five-file merge diff excludes unrelated work from the original local CLI branch. The original workspace and its
.autodevstate are preserved.