RFC6750 Java implementation

Java implemented utilities designed to RFC6750 specifications.

---

WWW-Authenticate Response Header

RFC2617

Auth Params

• realm

  RFC2617-1.2 RFC6750: The "realm" is OPTIONAL.
The "realm" attribute MUST NOT appear more than once.

• scope

  RFC6749-3.3 RFC6750: The "scope" is OPTIONAL.
The "scope" attribute MUST NOT appear more than once.

---

Error state auth-params

RFC6750 states:

If the protected resource request included an access token and failed authentication, the resource server SHOULD include the "error" attribute to provide the client with the reason why the access request was declined.
(Therfore these auth-params are optional.)
The "error", "error_description", and "error_uri" attributes MUST NOT appear more than once.

• error

  RFC6749-A.7

• error_description

  RFC6749-A.8

• error_uri

  RFC6749-A.9

Other auth-params

The auth-params listed so far are only the ones described in RFC6750. Custom auth-params or auth-params defined in related RFC's, like the ones references in this README, are also allowed; Those other auth-params are optional, and can occur more than once in the WWW-Authenticate response header unless otherwise outlined from the respective RFC in which they are defined.

Note on auth-param order within the WWW-Authenticate response header

The builder provided in this library imposes an order to the auth-params as they are present in the builder at the time of building. That order is the same as the order of appearance in this README which is the same order they are found in RFC6750.