Module oxide_auth::primitives::registrar

Registrars administer a database of known clients.

It will govern their redirect urls and allowed scopes to request tokens for. When an oauth request turns up, it is the registrars duty to verify the requested scope and redirect url for consistency in the permissions granted and urls registered.

Structs

BoundClient	A client and its chosen redirection endpoint.
Client	Clients are registered users of authorization tokens.
ClientMap	A very simple, in-memory hash map of client ids to Client entries.
ClientUrl	A pair of client_id and an optional redirect_uri.
EncodedClient	A client whose credentials have been wrapped by a password policy.
Pbkdf2	Store passwords using Pbkdf2 to derive the stored value.
PreGrant	These are the parameters presented to the resource owner when confirming or denying a grant request. Together with the owner_id and a computed expiration time stamp, this will form a grant of some sort. In the case of the authorization code grant flow, it will be an authorization code at first, which can be traded for an access code by the client acknowledged.
RegisteredClient	Recombines an EncodedClient and a PasswordPolicy to check authentication.

Enums

ClientType	Enumeration of the two defined client types.
RegistrarError	Handled responses from a registrar.

Traits

PasswordPolicy	Determines how passphrases are stored and checked.
Registrar	Registrars provie a way to interact with clients.