Child pages
  • ULX Teleconference 2010-11-22
Skip to end of metadata
Go to start of metadata


  • Time: 08:00 PT | 11:00 ET | 16:00 UTC/GMT | 18:00 CEST (Time Chart)
  • Skype: +9900827042954214
  • US Dial-In: +1-201-793-9022
  • Room Code: 295-4214


1) Roll Call


  1. Scott Cantor
  2. RL "Bob" Morgan
  3. Keith Uber
  4. Paul Trevithick
  5. John Bradley
  6. Benoit Bailleux

Voting, but not present:

  1. Axel Nennker

Not present

  1. Philippe Clement
  2. Gael Gourmelen
  3. Valeska O'Leary
  4. Trent Adams
  5. Bob Pinhero

Quorate meeting (6 of 6)

2) Minutes

Approved the following minutes (with Keith's correction that he was in fact present last week):

3) Trent's email

Wherein he suggested:

  1. We need to go through the mock-up code
    1. make sure the components used are compatible with our IPR regime for distribution
    2. insert into each file (HTML, JS, etc) the applicable copyright notice and reference to the license.
  2. Move the mock-up code into a subversion (or similar) repository so we can effectively start tracking version

Paul: This in process. Sounds like we'll use Google code as the repository.

4) ULX and the HTTP request header
  • Should we include ISA-related preference info in HTTP request header
  • Info
    1. the user's choice of cloud selector URL
    2. the user's active client selector capabilities (if present)
    3. the user's set of preferred service providers (e.g. IdPs)
  • How?
    • Long term: Browsers could build this in
    • Short term: a small browser extension could implement
  • Why?
    • Would provide a standard way for the user to exert their preference

Bob: #3 above could be provided by a minimally active client.

Scott: We're really trying to standardize a cookie. The SAML cookie got messed up in the transition from Liberty to Kantara. You have to have some way to describe the IdP.

Bob: ...yes and the user isn't going to expect to type in the IdP

Scott: Right

Bob: Hm...this is a "fish me here" cookie in essence.

Scott: This is a not a new idea. Issues include only making this go to the desired RPs, etc.

JohnB: This is like was a network-based cookie priming. I talked to them 3-4 months ago. It doesn't seem to have been made much progress. Lots of privacy/security issues.

Scott: Yes, if you take things a little bit too far ( folks realize that this isn't the right thing to do.

Scott: Because OpenID is purely redirect based, the RP may not know that there's an active client but there may be initiating the redirect.

Scott: What we're proposing here may be a more reasonable 1/2 way step. But the problem of making this other than just a cookie is that this raises the bar for RP a bit. OTOH this moves away from cookie nonsense a bit.

5) Role of the icons in the UX

Scott: It turns out the contrast between what Andreas was doing and what the latest Shib stuff is smaller than I realized. They already have found that there are cases where the text name of an IdP is the same, so having an icon there helps. I still don't love it but I see that there's an argument for adding an icon.

Bob: I'm not sure having an icon helps the discrimination, but hover text might help.

Scott: We've reached the stage where we need bring in a UX expert on this topic.

Bob: There's been a cultural gap between the discovery UIs that the few commercial providers (e.g. Janrain, etc) and things that have been done in spaces that have dozens or hundreds of more of IdPs that have stuck (in the past) with text. We're looking to bring these worlds together somehow.

Scott: I added the keywords element to the SAML Metadata Extention for User Interface spec.

Paul: AI: I'll talk to Valeska about this "role of the icons (and hover text) in the UI" in both the proposed "see all" and the "filtered view". We have questions like: What kinds of icons are going to be required based on different roles. The descriptive text is in this same bucket as the icons. For example, how do you discriminate between two IdPs have the same name (e.g. two universities with the same name (which has already shown up as a use case in the Shib world)).


Next Meeting (Nov 29th)

  • Time: 08:00 PT | 11:00 ET | 16:00 UTC/GMT | 18:00 CEST (Time Chart)
  • Skype: +9900827042954214
  • US Dial-In: +1-201-793-9022
  • Room Code: 295-4214
  • No labels