CRATEFIELD
Get started with Harness Join the waitlist

device-auth

The OAuth 2.0 device grant (RFC 8628): a CLI or a TV shows a code, a signed-in person approves it.

With cargo

cargo add cratefield-module-device-auth
crates.iodocs.rsSource

What it is

device-auth.

The OAuth 2.0 device authorization grant (RFC 8628) for a Cratefield venture: the flow for a client that has no browser and no keyboard — a CLI, a TV app, an appliance. It shows a short code, a signed-in person approves it in a browser, and the venture mints the credential.

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

  2. 0.3.1

    crates.ioReleaseDiff

    Other

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

  1. 0.3.0

    crates.ioRelease

    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.0

    crates.io

    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