Config

A message digest algorithm to be used. Usually only MD5 is supported by clients.

List of message digest algorithms to be used.

The charset to be used. If set to UTF-8, it will be passed in the WWW-Authenticate header.

A description of the provider that can be used for API documentation.

A name of the provider, or null for a default provider.

NonceManager to be used to generate nonce values.

Specifies a realm to be passed in the WWW-Authenticate header.

List of supported Quality of Protection (qop) options.

Configures a digest provider function that should fetch or compute message digest for the specified userName and realm. A message digest is usually computed based on username, realm, and password concatenated with the colon character ':'. For example, "$userName:$realm:$password".

Configures a digest provider function that should fetch or compute message digest for the specified userName, realm, and algorithm.

Adds an authentication filter to the list. For every application call the specified predicate is applied and if it returns true then the authentication provider is skipped (no auth required for this call with this provider).

Enables strict RFC 7616 compliance mode by setting the algorithms to SHA-512-256 and SHA-256, and charset to UTF-8.

Configures a resolver function for userhash support.

Sets a validation function that checks a specified DigestCredential instance and returns principal Any in a case of successful authentication or null if authentication fails.