Crate auth_service 

Auth service: campaigns, the devices admitted to them, and short-lived tokens for the other services. See edda-auth for the cryptography. Several instances can run against the same database.

Re-exports

pub use store::Store;

Modules

admin

Errors, as responses. What whoever runs the service asks of it over HTTP. The auth service’s admin API (see edda_server::admin): creating a campaign with its DM’s setup code, a new setup code, what a campaign may keep and do, exporting and importing a campaign with its devices, and deleting one.

error

pairing

Relaying pairing messages. See edda_auth::pairing for the protocol.

routes

Setting up campaigns, logging in, and devices.

store

Persistence in Postgres.

Structs

ApiDoc

The service’s OpenAPI description.

Functions

app

The service, within limits (its campaigns’ devices, and how often clients may try to sign in), signing tokens with token_key, or with the key kept in its database if None.

connect

Connects to the database, creating it if needed, and applies migrations.