@@ -465,7 +465,7 @@ \subsubsection{\mbox{\tt ivoa\_x509}}\label{sec:ivoa-x509}
465465
466466If the client does not hold any such certificate,
467467and the \verb |access_url |/\verb |standard_id | pair is present,
468- it may obtain one by presenting a username and password
468+ it may obtain one by presenting credentials
469469to the endpoint given by the \verb |access_url | parameter,
470470in the form defined by the \verb |standard_id | parameter.
471471If authentication is successful, a 200 OK response must be returned
@@ -901,10 +901,13 @@ \subsection{Mandatory authentication with certificates}
901901is required to access the service.
902902The \verb |Bearer | challenge (\rfc {6750}) means we can authenticate with
903903a Bearer Token if we have or know how to get one, but we don't.
904- The unparameterised \verb |ivoa_x509 | challenge means we can authenticate
905- with a certificate if we have one, but we don't.
906- We can however use the parameterised \verb |ivoa_x509 | challenge
907- (Section~\ref {sec:ivoa-x509 }) which informs how to acquire
904+ The unparameterised \verb |ivoa_x509 | challenge means
905+ the client can, in principle, authenticate with a certificate
906+ from any valid CA and not just one issued by the endpoint in the
907+ parameterised challenge.
908+ Without having such a certificate however we can use
909+ the parameterised \verb |ivoa_x509 | challenge
910+ (Section~\ref {sec:ivoa-x509 }) which advises one way to acquire
908911a suitable certificate.
909912It has a \verb |standard_id | of \verb |BasicAA | (Section~\ref {sec:standard-id })
910913so we transmit user credentials using
0 commit comments