45 Oaklands Wood Hatfield Hertfordshire AL10 8LU United Kingdom +44 (0)1707 258219 nickshanks@nickshanks.com http://nickshanks.com/

This document defines the "Form" HTTP authentication scheme. It allows web developers access to standard HTTP-based authentication mechanisms whilst retaining control over the look and feel of their log-in page, without requiring any client-side scripting. Comments are requested and should be addressed to the author.

This document builds upon the Digest authentication scheme defined by and amended by , but changes the process for creating the A1 value (as is defined by Section 3.2.2.2 of ), and defines different user agent behaviour. It is intended to allow migration away from application/x-www-form-urlencoded requests over unencrypted HTTP which transmit the password in plaintext; and to do so in a way that, when widely supported by user agents and server software, will also allow simple migration from Digest authentication, should developers who are already using that want to take control of the credentials solicitation appearance. It is not intended for use in conjunction with TLS, as it offers little benefit there, but nothing prevents its use in that context if so desired.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

Supporting user agents MUST present to the user (or to a software/hardware agent acting on behalf of the user) the body of a response which uses either a HTTP status code of 401 and a WWW-Authenticate header specifying the "Form" scheme; or a 407 status code and a Proxy-Authenticate header specifying the "Form" scheme. This response body MUST contain a form in a format that the user agent can understand, e.g. HTML <form> element with <input> children, XML incorperating XForms <xf:input> elements, or other comparable markup which the user agent knows about. If the response does not meet these conditions, then the user agent MUST ignore this document and process the response as it would otherwise. When submitting the form, instead of obeying the action, method and encoding specified by the form, user agents MUST create an Authorization header by concatenating the values of each form input, in document order, each seperated from the next by a single colon character ":" not surrounded by whitespace, possibly followed by nonce and cnonce values also seperated by a colon character, then computing the hash of the resulting string using the MD5 algorithm, or otherwise per the algorithm parameter (e.g. those defined by ). When no nonce value is provided by the server

A1 = *(unq(form-field-value) ":") unq(form-field-value)

If a nonce value is provided by the server

A1 = H( *(unq(form-field-value) ":") unq(form-field-value) ) ":" unq(nonce-value) ":" unq(cnonce-value)

The result now forms the "A1" input to the standard Digest authentication computation Section 3.2.2.1 of RFC2617. The user agent MUST then re-submit the original request with this header included, to the original Request-URI Section 5.1.2 of RFC2617. This scheme introduces no new authentication parameters.

This section is non-normative. An example in HTML:

<form action=/login.php method=POST> <input name=user required> <input name=realm type=hidden value=admin> <input name=pass type=password required> <input name=pin type=password size=4> <button>Log In</button> </form>

When filled out by the user (or acting agent) with values of user=dave, pass=p455w0rd and pin=9876, and assuming the default MD5 algorithm is to be used, this form will result in an Authorization header being generated by conforming user agents by means of computing the function H(A1) = md5(dave:admin:p455w0rd:9876), then combining that with qop, nonce and other parameters as per . An empty field results in an empty string being concatenated, with no special treatment, i.e. if no value for the PIN were provided in the above example, the MD5 hash would be computed as md5(dave:admin:p455w0rd:). An empty value between two others would result in a double colon appearing in the string to be hashed, "::". The input names, if provided, are not used in any way. They serve only as fallback for UAs that do not support this document. In the above case, user agents which do not support this document are expected to send a POST request to the path /login.php with the form fields URL-encoded in the request body. This allows for incremental support to be introduced as user agents are released which support this document and users upgrade.

Yet to be written (mostly). All security considerations in pertaining to Digest authentication method apply to the Form method too. Until such time as standard server software (such as Apache, Lighttpd, Nginx, etc.) nativly supports this authentication scheme, web developers will have to implement support using server-side processing langauges (such as Ruby, Node.js or PHP). All incoming requests to URIs beyond the authentication point will need to be caught and processed for authentication credentials, to avoid exposing valid URIs from invalid ones. It is expected that third-party libraries will be developed to ease this.

IANA is to register the "Form" authentication scheme, citing of this document as the reference, within the http-authschemes registry at <http://www.iana.org/assignments/http-authschemes> as established by Section 2.3 of .

Authentication scheme name: Form Specification text: This document Notes: A variant of the Digest authentication scheme, with new processing requirements for the server and the user agent.

Server requirements and User Agent requirements are inter-mixed in , and both are poorly defined. How should the realm, and other authentication header parameters, be reflected in the form. Should form fields with the same name as a parameter adopt the value of the parameter in supporting UAs? The value of the form field will be submitted to the action URI by old UAs. Should this be true only for "realm"?