Skip to content

Prepare dev Identity RS256 verification and issuer policies - #69

Open
jmgasper wants to merge 2 commits into
devfrom
feat/dev-identity-rs256
Open

jmgasper wants to merge 2 commits into
devfrom
feat/dev-identity-rs256

Conversation

@jmgasper

@jmgasper jmgasper commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Prepare this service to verify Identity RS256 access tokens through its dedicated JWKS endpoint while retaining the dev Auth0 and machine issuers. Pin tc-core-library-js 4.0.0-rc.4 at immutable commit c7c8fab502b7152dd06b1ce46cdb703e0e13b357, update the lockfile, and add the proposed dev policy and rollout notes.

Leave open: coordinate configuration before merging/deploying. The key and public settings are staged under /config/identity-rs256-dev-staged/; running services do not consume them. This verifier removes implicit HMAC trust and enforces verified human identities and bounded token lifetimes. Any temporary HS256 issuer needs an explicit finite retirement deadline. Do not deploy this dependency change without its intended policy. See docs/identity-rs256-dev.md. Production configuration is outside this rollout.

Targets the active dev deployment branch as agreed.

Validation: frozen dependency installation and service build passed. The shared verifier passed 47 tests and lint separately. Live RS256 activation and end-to-end login testing are deferred until the coordinated rollout.

Additional validation: 532 tests passed; three pre-existing skipped tests remain skipped. Human and machine test issuers now use separate explicit policies.

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