Skip to content

feat(oidc): enforce strict transport defaults - #3

Closed
danifronter wants to merge 1 commit into
mainfrom
codex/strict-oidc-transport
Closed

feat(oidc): enforce strict transport defaults#3
danifronter wants to merge 1 commit into
mainfrom
codex/strict-oidc-transport

Conversation

@danifronter

Copy link
Copy Markdown
Contributor

What changed

  • Enforces TLS verification, bounded timeouts and no redirect following for discovery, token and JWKS calls.
  • Adds safe correlation-ID propagation for OIDC backchannel requests.
  • Rejects non-HTTPS discovered OIDC endpoints.

Why

Consumers need a verifiable transport boundary before production OIDC adoption.

Validation

  • composer test
  • composer analyse
  • composer audit --no-interaction
  • composer validate --strict
  • git diff --check

Release

This remains a draft. After review, publish a semantic v1.2.0 tag and update each consumer lock file in its own reviewed PR.

@danifronter

Copy link
Copy Markdown
Contributor Author

Superseded by #5, which completed the reviewed Identity SDK 2.0 transport and DPoP work and was released as v2.0.0. Closing this earlier draft to keep one authoritative upgrade path.

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.

1 participant