Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Wants to sign-in to the NIH site
  • Has never been to this NIH site before
  • Alice already Already has a multi-protocol browser add-on (aka selector, smart client, etc.)
  • Has configured her add-on with:
    • OpenID: Yahoo, AOL, Google, Facebook
    • SAML: Ohio State
    • Infocard: Equifax Identity Card, PayPal
  • Is not logged in to any of her OpenIDs or SAML IdPs at the moment
  • Has not defined a "default" OpenID, SAML or InfoCard

...

    1. The addon reads some data that tells it stuff like:
    2. That the site is an RP for OpenID, IMI and SAML protocols (unusually it does not support username/password!)
    3. The list of attributes that the site wishes to receive and for each attribute the list of authorities that the RP trusts. In our case the site is going to request only a non-correlateable identifier (aka an IMI "PPID", OpenID "directed" identity, SAML "persistent" NameID) and that it trusts only Yahoo, AOL, Google, as well as Facebook, Equifax, Citigroup, Silicon Wave, Acxiom, and InCommon IdPs to issue this attribute
  1. The add-on displays a login window.
    1. It prominently shows the following accounts that could be used immediately (because Alice has these accounts and the NIH site accepts these accounts):
      1. Google
      2. Ohio State
      3. Yahoo
      4. Equifax
      5. AOLPayPal
    2. Its also shows accounts that Alice could use if she first registered with these IdPs
      1. Acxiom
      2. Wave Systems
      3. Citigroup
  2. Alice clicks on Google
  3. Alice authenticates to Google
  4. Alice agrees to share Google attributes with NIH

...