Again, I don't wish to be the OpenID advocate, but I appear to be in that role again...

This technology is really only meant to replace the account setup and user email portion of the registration process. The crypto systems employed are to prevent spoofing mostly. The idea is to lower the bar so people can join your site without any effort. Really, if I have to sign up for another forum to make one post I'm going to explode.

If you used your OpenID to log into a bank, the openid is really just in place of the email for the signup. It also transmits a few signup details for you (like email, real name, nickname, etc) and then the bank would ask you to configure a second factor for secure signon. First, they'd have to verify your identity matched, and then they'd ask you to set up another password (a secure one or a USB key, or a certificate or whatever) that you'd use to access your bank software.

So the single point of failure isn't an end user security problem, only a sign-on problem.

What we're having here is a semantic argument about Authentication vs Authorization. They're different, but when we say authentication we usually and implicitly mean both.

-Paul

In reply to Re^4: Concerning Single Sign-on, Bitcard (TypeKey), and OpenID, CACERT client certificate by jettero
in thread Concerning Single Sign-on, Bitcard (TypeKey), and OpenID by jettero

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.