Re: [PATCH v3 00/11] Enhance credential helper protocol to include auth headers

From: M Hickford <mirth.hickford@gmail.com>
Date: Nov 3, 2022, 19:00 UTC
Message-ID: <CAGJzqs=o2O+W=Uecu+TJ0Nuw7FsehocKu4Dyko2iKdz5HyiKrA@mail.gmail.com>
In-Reply-To: <pull.1352.v3.git.1667426969.gitgitgadget@gmail.com>

On Wed, 2 Nov 2022 at 22:09, Matthew John Cheetham via GitGitGadget <gitgitgadget@gmail.com> wrote:

Show 12 quoted lines

>
> `authtype`::
>
> Indicates the type of authentication scheme that should be used by Git.
> Credential helpers may reply to a request from Git with this attribute,
> such that subsequent authenticated requests include the correct
> `Authorization` header.
> If this attribute is not present, the default value is "Basic".
> Known values include "Basic", "Digest", and "Bearer".
> If an unknown value is provided, this is taken as the authentication
> scheme for the `Authorization` header, and the `password` field is
> used as the raw unencoded authorization parameters of the same header.

Do you have an example using authtype=Digest? Would the helper populate the password field with the user's verbatim password or the Digest challenge response? Put another way, is the Digest challenge-response logic in Git (libcurl) or the helper?

https://www.rfc-editor.org/rfc/rfc7616#section-3.4