auth

Types

AuthScheme

4.4. Client Credentials Grant 4.4.2. Access Token Request https://datatracker.ietf.org/doc/html/rfc6749#section-4.4.2

The client MUST authenticate with the authorization server as described in Section 3.2.1.

3.2.1. Client Authentication https://datatracker.ietf.org/doc/html/rfc6749#section-3.2.1

Confidential clients or other clients issued client credentials MUST authenticate with the authorization server as described in Section 2.3 when making requests to the token endpoint.

2.3.1. Client Password https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1

AuthHeader

Clients in possession of a client password MAY use the HTTP Basic authentication scheme as defined in [RFC2617] to authenticate with the authorization server. The client identifier is encoded using the “application/x-www-form-urlencoded” encoding…

RequestBody

Alternatively, the authorization server MAY support including the client credentials in the request-body (client_id and client_secret).

pub type AuthScheme {
  AuthHeader
  RequestBody
}

Constructors

```
AuthHeader
```
```
RequestBody
```

Functions

add_auth

</>

pub fn add_auth(rb: RequestBuilder(a), client: Client(b), auth_scheme: AuthScheme) -> RequestBuilder(
  a,
)

add_auth_to_body

</>

pub fn add_auth_to_body(client: Client(a), rb: RequestBuilder(b)) -> RequestBuilder(
  b,
)

add_basic_auth_header

</>

pub fn add_basic_auth_header(client: Client(a), request: Request(
    b,
  )) -> Request(b)

Add to authorization header for basic auth.

encode_auth

</>

pub fn encode_auth(client: Client(a)) -> String