CRATEFIELD
Get started with Harness Join the waitlist

oauth-client

OAuth 2.0 over the HttpClient port: authorize URLs, code exchange, refresh, revocation, PKCE.

With cargo

cargo add cratefield-oauth-client
crates.iodocs.rsSource

What it is

oauth-client.

OAuth 2.0 for the harness (issue #531): the authorize URL, the code exchange, the refresh and the revocation, spoken once over the harness's HttpClient port — so a module runs it unchanged on Workers and native. No provider SDK, no discovery document: the provider's three URLs are configuration.

From the crate’s own README.

History

Changelog.

From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 4 versions recorded, newest first. Every published version is on crates.io.

  1. 0.3.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core, cratefield-testing

  2. 0.3.1

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
2 earlier versions 0.2.1 to 0.3.0

  1. 0.3.0

    crates.ioReleaseDiff

    Changed

    • Breaking: requires cratefield-core 0.8 (was 0.7), and so a minor rather than a patch bump: a venture still on core 0.7 does not pick this release up through a caret requirement and end up with two copies of core (#712).

    Other

    • updated the following local packages: cratefield-core

  2. 0.2.1

    crates.ioRelease

    Other

    • OAuth 2.0 device authorization grant (RFC 8628) issuing a venture-defined credential (#587) (#633)

One of 76 crates in the harness, all of them MIT and all of them in one repository.

Join the waitlist All modules