Concordia telecon 18 Mar 2008

From Project Concordia

Jump to: navigation, search

Contents

Attendance

Eric Tiffany & Dervla O'Reilly (Liberty Alliance), Scott Cantor (Internet2), Mike Jones (Microsoft), Ari Kermeier (Oracle), Asish Jain (Ping Identity), Vijay Simha (FuGen Solutions), Paul Madsen (NTT), Damian Karu (Oracle), Sampo Kellomaki (Symlabs), Pat Patterson (Sun Microsystems)

Scenario 1

Attributes specifics (Copy CardSpace claims)

Sampo: Also possibly bootstrap info

Scott: but that requires other participants to

Scenario 2

What is the content of the message passed through the gateway? The gateway will need to extract the claims and repackage into the new assertion. Can someone edit the scenario to clarify the flow and details? Scenario should be explicit that the bridge needs to rewrite the messages according to the SAML / WS-FED reqs. Also need to translate the requests (in so far as possible) from one protocol to the other. NameID is not needed. Not full translation, but just enough to make it work.

Scenario extensions

Adding Web Services call. Also, DK scenario using WS-Trust and WSF hybrid. No objections.

AV/Logistics/Registration

Network logistics

  • Symlabs - prefer internet version
  • Oracle - prefer internet version
  • Microsoft - ONLY hosted, no stuff on site.

Conclusion that we'll have all solutions hosted externally, and hope the network stays up.

Signage/banners

Directional signage to room provided by RSA

Signage outside room with logos of everyone participating.

Suggestion to have a large banner inside the room with everyone participating. Dervla will copy participants on proofs to verify logos for signage.

Access on Sunday, April 6

All attendees on today's call will be onsite Sunday at 1pm PST with the exception of Asish Jain arriving on Sunday evening.

Equipment supplied

Each table-top will have the following:

  • 1 x 21” LCD monitor
  • Internet connectivity internet (note: no Wi-Fi access in this room)
  • Power
  • 1 x power strip (6 outlets)
  • 1 x 1.5' x 8' classroom table
  • Network cables
  • USB keyboard and mouse (LAPs)
  • White table top and black skirting. No additional banners/signage are recommended, would like to keep the look and feel uniform.

Collateral

All agreed we should have a 1-2 page datasheet, each vendor table could add their own materials if need be. (Eve is working on this.)

Registration

Workshop registration is currently at 616. Room layout is theatre, we are at capacity and registration has been capped. We may see some drop off onsite, but will also see wanderers.

Workshop hours

9am-12:30pm. Help is needed to shuffle attendees from the room on time as the Liberty Alliance workshop takes place in the same room beginning 1pm. (The room setting will not change for the 1pm workshop.)

Suggested agenda and presentation flow

As sent by Eve to the list:

1. Intro front-of-house projection that hits on everything being presented and who's who. ~ 1hour

2. Turn the attendees loose on the demo pods, but in parallel begin...

3. A round robin featurette of each implementation so they get air time with the "big" audience vs. only having airtime with the bodies they can pack around their pod. But the other significant aspect to the round-robin sessions is having our "user chair" [that'll be Bob Haar -elm] interview them and moderate Q&A with that implementer from the audience. This is the "conversation" thread across all implementations that will lead to...

4. At the end of the sessions we reserve about 30 minutes for the "user chair" to lead a panel discussion of deployers (picked either during the session or ahead of time) to evaluate/grade the Concordia progress demonstrated and offer input on where Concordia needs to head next (and with what prioritization/urgency)." This makes best use of everyone's time and gives everyone attending a chance to see, learn, and contribute something interesting. Since we'd like to re-emphasize the role of deployer input around now, as I already noted on a previous call, this also gives Bob H. a clear role- model and organizing function.

All agreed this flow works well, discuss further via email.