Yadis

Identity, trust and the plumbing of the webยทon the home of the Yadis discovery protocol since 2005

Archive · Yadis wiki

5 Examples

From the archiveThis page is part of the working wiki of the Yadis discovery protocol, kept here as it was written by the project’s participants in 2005–2006. It is preserved for the record and is not maintained as current documentation. All archived pages →

(These two examples were specified following Yadis Specification 0.5. They are still to be revised to conform to Yadis Specification 1.0. --jm)

5.1 Log on at an OpenID site (non-delegated case)

  1. Action: User enters URL of Relying Party into browser; browser requests page from Relying Party.
    Response: Relying Party's page is displayed in browser.
  2. Action: User enters their Yadis ID (which in this case is an OpenID URL), into the login field; clicks LogOn.
    Response: Control gets handed to the Relying Party.
  3. Action: Relying Party performs a Yadis request on the Yadis URL.
    Response: HTML page is returned, which contains identity.server field.
  4. Action: Relying Party performs a Yadis request on the URL in the identity.server field.
    Response: A Yadis document of MIME type application/xrds+xml is returned, which lists http://openid.net/ as one of the supported service types.
  5. Action: Relying Party interacts with the provided URL (which now has been identified as an OpenID URL) using the OpenID protocol.
    Response: The browser session has been authenticated; the Relying Party sends the logged-on page to the browser; control returns to the user.

5.2 Log on at a LID site (non-delegated case)

  1. Action: User enters URL of Relying Party into browser; browser requests page from Relying Party.
    Response: Relying Party's page is displayed in browser.
  2. Action: User enters their Yadis ID (which in this case is a LID URL) into the ID field; clicks LogOn.
    Response: Control gets handed to the Relying Party.
  3. Action: Relying Party performs a Yadis request on the Yadis URL.
    Response: A Yadis document of type application/xrds+xml is returned, which lists http://lid.netmesh.org/ as one of the supported service types.
  4. Action: Relying Party interacts with the provided URL (which now has been identified as a LID URL) using the LID protocol.
    Response: The browser session has been authenticated; the Relying Party sends the logged-on page to the browser; control returns to the user.