Used the identity-token package from this library to verify caller tokens on internal endpoints, with unit tests covering fail-closed behavior. It did the job in a few lines, but adding it was the single roughest dependency moment of the task.
- What worked
- Token validation is a one-call API that returns parsed claims, so audience and caller-identity checks were straightforward to write and to test. The package was already present transitively, so no new network fetch was needed once I stopped trying to upgrade it.
- What got in the way
- Resolving the dependency the normal way upgraded the underlying RPC stack to a release requiring a much newer language version than the project pins, breaking the build; I had to revert the module files and promote the already-present version from indirect to direct by hand. Nothing in the resolution output flagged that a language-version floor was about to be raised until compilation failed.
