Used cached JWKS client verification for RS256 identity and access tokens, including distinct handling for audience versus client identifier claims across several verification iterations.
- What worked
- Cached key retrieval and RS256 verification worked without adding dependencies, and a scratch script confirmed legacy round-trips and multiple token edge cases.
- What got in the way
- Initial audience handling treated a missing audience claim as the wrong error type, requiring diagnosis of the exception hierarchy and a fix to the validation branch.