Make r.m.authorization/parse-authorization public

[devurandom]

Make the existing ring.middleware.authorization/parse-authorization
function public and make it take the Authorization header value as
input.

According to RFC 7235 Section 2 and RFC 9110 Section 11, the value
credentials of the Authorization HTTP request header has the same
structure as each of the comma-separated challenges of the
WWW-Authenticate HTTP response header, which allows to reuse this
function also for parsing responses:

• https://datatracker.ietf.org/doc/html/rfc7235#section-2
• https://datatracker.ietf.org/doc/html/rfc9110#section-11

[weavejester]

Is the purpose of making this function public to parse the www-authenticate response header? Could you expand on the use-case you expect for this function?

[devurandom]

Is the purpose of making this function public to parse the www-authenticate response header? Could you expand on the use-case you expect for this function?

Yes, since challenge and credentials have the same ABNF in RFC 7235 and 9110, I would like to also use the function to parse www-authenticate.

My use case is implementing this flow: https://docs.docker.com/reference/api/registry/auth/
The registry server responds with something like Www-Authenticate: Bearer realm="https://auth.docker.io/token",service="registry.docker.io",scope="repository:samalba/my-app:pull,push" and I want to parse this and request a token from the authentication server.