3.2.5.1.2 Response
The server issues a challenge using an HTTP response with the following characteristics.
|
HTTP response |
Value |
|---|---|
|
Response code |
302 Found [RFC2616] |
|
Header: Location |
urn:http-auth:PKeyAuth?Nonce=<Challenge-nonce> &CertAuthorities=<cert-authorities>&Version=1.0 &SubmitUrl=<Submit-url>&Context=<Server-state> |
Challenge-nonce: A short-lived nonce.
cert-authorities: A semicolon-delimited list of URL-encoded issuer names. The client must prove possession of the private key of a certificate that was issued by one of these issuers.
Submit-url: The URL to which the client MUST submit its response to the server's challenge. The server uses the same URL to which the client submitted its request (section 3.1.5.1.1).
Server-state: Context information that the client will play back to the server to complete this protocol sequence. This information is in the form of opaque binary data that cannot be deciphered by the client.