A class which registers middleware (via .use()) and then processes inbound requests against that middleware (via .listen()).

The authorization code grant type. https://datatracker.ietf.org/doc/html/rfc6749.html#section-4.1 This grant supports PKCE. https://datatracker.ietf.org/doc/html/rfc7636#page-9 Clients must use PKCE in order to detect and prevent attempts to inject (replay) authorization codes in the authorization response. https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics#section-2.1.1

The client credentials grant type. https://datatracker.ietf.org/doc/html/rfc6749.html#section-4.4

Provides context about the current request and response to middleware functions, and the current instance being processed is the first argument provided a Middleware function.

An interface which allows setting and accessing cookies related to both the current request and response. Each Context has a property .cookies which is an instance of this class.

The refresh token grant type. https://datatracker.ietf.org/doc/html/rfc6749.html#section-6

An interface to control what response will be sent when the middleware finishes processing the request.

An interface for registering middleware that will run when certain HTTP methods and paths are requested, as well as provides a way to parameterize parts of the requested path.

A basic implementation of scope.

The authorization server encountered an unexpected condition that prevented it from fulfilling the request.

The token type is not supported by the authorization server.

The default allowed PKCE code challenge methods. Clients SHOULD use PKCE code challenge methods that do not expose the PKCE verifier in the authorization request. Currently, "S256" is the only such method. https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics#section-2.1.1

Generates url for an authorization get request.

CREDIT: https://gist.github.com/enepomnyaschih/72c423f727d395eeaa09697058238727 Encodes a given Uint8Array, ArrayBuffer or string into RFC4648 base64 representation

Generates a random code verifier with a minimum of 256 bits of entropy. This is done by generating a random 32-octet sequence then base64url encoding it to produce a 43 octet URL safe string. https://datatracker.ietf.org/doc/html/rfc7636#section-7.1

Generates random salt. The length is the number of bytes.

Hashes a password with salt using the PBKDF2 algorithm with 100k SHA-256 iterations.

Used for redirecting to login page for the authorization code flow.

The tagged type for "form" bodies.