Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In addition to the meta tag sample by Otto, you should be aware whether your provider supports OpenID 2.0 (there are numerous improvements). If it does use meta tags as the following:</p> <pre><code>&lt;link rel="openid2.provider" href="http://www.loginbuzz.com/provider.axd" /&gt; &lt;link rel="openid2.local_id" href="http://example.loginbuzz.com/" /&gt; &lt;link rel="openid.server" href="http://www.loginbuzz.com/provider.axd" /&gt; &lt;link rel="openid.delegate" href="http://example.loginbuzz.com/" /&gt; </code></pre> <p>A good idea would also be to use secure links, but this could limit some relying parties from signing in. This could however be solved by providing a <a href="http://en.wikipedia.org/wiki/XRDS" rel="nofollow noreferrer" title="XRDS on Wikipedia">XRDS document</a>.</p> <p>The really neat thing about XRDS is that you are able to specify multiple providers in this document. Say you have a bunch of different accounts all with different providers supporting different extensions. The relying party are then able to select the best match by itself. In the XRDS document you could also specify multiple URLs for each service, so that https is used when appropriate.</p> <p>I would also recommend buying an <a href="http://www.inames.net/personal.html" rel="nofollow noreferrer" title="More on personal i-names">i-name</a> as it by design is more secure (the canonical ID - the i-number - associated with an i-name belongs to you even if the i-name expires).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload