|
3 | 3 | \input gitmeta |
4 | 4 | \usepackage[textsize=small,textwidth=3.8cm,backgroundcolor=yellow]{todonotes} |
5 | 5 |
|
6 | | -\title{IVOA Interoperable Authentication Management} |
| 6 | +\title{IVOA Interoperable Authentication Protocol} |
7 | 7 |
|
8 | 8 | % see ivoatexDoc for what group names to use here; use \ivoagroup[IG] for |
9 | 9 | % interest groups. |
|
25 | 25 | \begin{document} |
26 | 26 |
|
27 | 27 | \begin{abstract} |
28 | | -IVOA's Interoperable Authentication Management explains how |
| 28 | +IVOA's Interoperable Authentication Protocol explains how |
29 | 29 | VO services can manage the authentication process for |
30 | 30 | interoperability with clients, especially non-browser clients. |
31 | 31 | Particularly, this document |
|
36 | 36 | \end{abstract} |
37 | 37 |
|
38 | 38 |
|
39 | | -\todo{The title is up for debate. |
40 | | - Sara/Dave suggest maybe Interoperable Authentication Protocol instead? |
41 | | - Or something else. |
42 | | - BM: "Protocol" may be better than "Management" so it's IAP, instead of |
43 | | - IAM, which is a term in this same field meaning |
44 | | - "Identity and Access Management".} |
45 | | - |
46 | | - |
47 | 39 | \section*{Acknowledgments} |
48 | 40 |
|
49 | 41 |
|
@@ -190,7 +182,7 @@ \subsection{Role within the VO Architecture} |
190 | 182 | Fig.~\ref{fig:archdiag} shows the role this document plays within the |
191 | 183 | IVOA architecture \citep{2021ivoa.spec.1101D}. |
192 | 184 |
|
193 | | -IVOA-IAM provides a way to advertise authentication methods |
| 185 | +IAP provides a way to advertise authentication methods |
194 | 186 | associated with existing VO services. |
195 | 187 | For services like TAP \citep{2019ivoa.spec.0927D} |
196 | 188 | that comply with VOSI \citep{2017ivoa.spec.0524G} to |
|
0 commit comments