cratefield-auth-client 0.3.4

Verify auth-service tokens in a consuming app: JWKS fetch and cache, ES256 verification, and an axum extractor (issue #11)
Documentation
<p align="center">
  <a href="https://github.com/Cratefield/harness">
    <img src="https://raw.githubusercontent.com/Cratefield/harness/main/assets/banners/cratefield-auth-client.png" alt="cratefield-auth-client — Who the caller is." width="100%">
  </a>
</p>

<p align="center">
  <a href="https://crates.io/crates/cratefield-auth-client"><img src="https://img.shields.io/crates/v/cratefield-auth-client.svg?style=flat-square&labelColor=0A0A0B&color=4C6FFF" alt="cratefield-auth-client on crates.io"></a>
  <a href="https://docs.rs/cratefield-auth-client"><img src="https://img.shields.io/docsrs/cratefield-auth-client?style=flat-square&labelColor=0A0A0B&color=EDEBE6" alt="cratefield-auth-client documentation"></a>
  <a href="https://github.com/Cratefield/harness/blob/main/LICENSE"><img src="https://img.shields.io/badge/LICENSE-MIT-4C6FFF?style=flat-square&labelColor=0A0A0B" alt="MIT"></a>
</p>

# cratefield-auth-client

Verify auth-service tokens in a consuming app: JWKS fetch and cache,
ES256 verification with the audience check that hand-rolled verifiers
forget, and an axum extractor. Issue #11.

---

MIT. Part of the [Cratefield harness](https://github.com/Cratefield/harness).