<?xml-stylesheet href='/static/xsl/oai.xsl' type='text/xsl'?>
<ri:Resource created="2015-12-04T11:39:00" status="active" updated="2023-05-23T14:03:00" version="1.2" xmlns:ri="http://www.ivoa.net/xml/RegistryInterface/v1.0" xmlns:vstd="http://www.ivoa.net/xml/StandardsRegExt/v1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ivoa.net/xml/StandardsRegExt/v1.0 http://vo.ari.uni-heidelberg.de/docs/schemata/StandardsRegExt.xsd" xsi:type="vstd:Standard">

  <title>IVOA Single-Sign-On Profile: Authentication Mechanisms</title>
  <identifier>ivo://ivoa.net/std/sso</identifier>
  <curation>
    <publisher>IVOA</publisher>
    <creator>
      <name>Taffoni, G.</name>
      <logo>http://www.ivoa.net/icons/ivoa_logo_small.jpg</logo>
    </creator>

    <creator>
      <name>Schaaff, A.</name>
    </creator>

    <creator>
      <name>Rixon, G.</name>
    </creator>

    <creator>
      <name>Major, B.</name>
    </creator>

    <date role="representative">2017-05-24</date>
    <date role="updated">2017-05-24</date>
    <version>2.0</version>
    <contact>
      <name>IVOA GWS WG</name>
      <email>grid@ivoa.net</email>
    </contact>
  </curation>
  <content>
    <subject>virtual observatory</subject>
    <description>
      Approved client-server authentication mechanisms are described for the
      IVOA single-sign-on profile: No Authentication; HTTP Basic
      Authentication; TLS with passwords; TLS with client certificates;
      Cookies; Open Authentication; Security Assertion Markup Language; OpenID.
      Normative rules are given for the implementation of these mechanisms,
      mainly by reference to pre-existing standards. The Authorization
      mechanisms are out of the scope of this document.
    </description>
    <referenceURL>http://www.ivoa.net/Documents/SSOAuthMech</referenceURL>
  </content>
  <endorsedVersion status="rec">2.0</endorsedVersion>

  <key>
    <name>BasicAA</name>
    <description>
      Service supports authentication with HTTP basic authentication
      (RFC2617, sect. 4 of the Recommendation).
    </description>
  </key>
  <key>
    <name>tls-with-password</name>
    <description>
      Service supports authentication with a password transmitted through TLS
      as per section 7 of the Recommendation.
    </description>
  </key>
  <key>
    <name>tls-with-password</name>
    <description>
      Service supports authentication with a password transmitted through TLS
      as per section 7 of the Recommendation.
    </description>
  </key>

  <key>
    <name>tls-with-certificate</name>
    <description>
      Service supports authentication with a client-side X.509 certificate
      as per section 6 of the Recommendation.
    </description>
  </key>
  <key>
    <name>cookie</name>
    <description>
      Service supports authentication with RFC 6265-type cookies
      as per section 8 of the Recommendation.
    </description>
  </key>
  <key>
    <name>saml2.0</name>
    <description>
      Service supports authentication via SAML (most likely, "Shibboleth")
      as per section 9 of the Recommendation.
    </description>
  </key>
  <key>
    <name>OAuth</name>
    <description>
      Service supports authentication via Open Authentication 2.0 ("OAuth")
      as per section 10 of the Recommendation.
    </description>
  </key>
  <key>
    <name>OpenID</name>
    <description>
      Service supports authentication via OpenID
      as per section 11 of the Recommendation.
    </description>
  </key>

</ri:Resource>