CRATEFIELD
Get started with Harness Join the waitlist

connections

Per-person third-party OAuth connections: authorize, sealed tokens, refresh and revoke.

With cargo

cargo add cratefield-module-connections
crates.iodocs.rsSource

What it is

connections.

Per-subject third-party OAuth connections for a Cratefield venture: a person authorizes an account at a provider, both tokens are sealed at rest, and the venture can hand out a live access token, refresh it before it lapses, or revoke the whole connection.

From the crate’s own README.

History

Changelog.

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

  1. 0.2.3

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core, cratefield-oauth-client

  2. 0.2.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
3 earlier versions 0.1.0 to 0.2.1

  1. 0.2.1

    crates.ioReleaseDiff

    Fixed

    • thirteen error-handling defects, plus make the guard-script tests survive a non-executable checkout (#828)

  2. 0.2.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

  3. 0.1.0

    crates.ioRelease

    Other

    • per-account third-party OAuth connections with sealed tokens, refresh and revoke (#624) (#638)

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

Join the waitlist All modules