Repository navigation
Release 1.3.2: bound complete OIDC token exchanges - #44
Merged
Merged
Conversation
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.
A token endpoint could trickle response bytes and extend authentication beyond the configured five-second budget. The exchange now runs in a bounded helper with cleanup on deadline, while retaining verified TLS, response limits, refusal semantics and no redirects or retries.
This release updates both client/server metadata, changelog and user release notes. Five real loopback regressions cover normal exchange, slow headers/body, redirect/refusal and malformed/oversized responses. Installed-release acceptance verifies the transport module bytes and runs these cases outside the checkout.
Local Python 3.12: 240 cases collected; unittest reports 240 cases with two Redis integration skips because no local Redis URL was configured. The existing CI Redis job remains enabled. Strict user/contributor Sphinx build passed.
Publish both Python packages, the versioned Docker image and matching GitHub release only after CI succeeds.