Skip to content

Commit 54bbae4

Browse files
committed
Adjust wording following Pat's suggestions
1 parent eaae5c3 commit 54bbae4

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

AuthVO.tex

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -465,7 +465,7 @@ \subsubsection{\mbox{\tt ivoa\_x509}}\label{sec:ivoa-x509}
465465

466466
If the client does not hold any such certificate,
467467
and 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
469469
to the endpoint given by the \verb|access_url| parameter,
470470
in the form defined by the \verb|standard_id| parameter.
471471
If authentication is successful, a 200 OK response must be returned
@@ -901,10 +901,13 @@ \subsection{Mandatory authentication with certificates}
901901
is required to access the service.
902902
The \verb|Bearer| challenge (\rfc{6750}) means we can authenticate with
903903
a 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
908911
a suitable certificate.
909912
It has a \verb|standard_id| of \verb|BasicAA| (Section~\ref{sec:standard-id})
910913
so we transmit user credentials using

0 commit comments

Comments
 (0)