Versions Compared

Key

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

...

From
ToTopic
09:00-09:30Welcome, Introductions & Expectations
09:30-10:00OIDCfed & Federations (results survey) (10 min),
Discussion on what's needed & feedback (20min)
10:00

-

12:00

OIDCfed Specification (15 min),
Discussion on what's need needed & feedback (90min)
Coffee break (15min somewhere in 2 hour15m between 10:45 and 11:00)

12:00-1312:0030Determine Open Space topics
12:30Lunch13:00

-

13:30Determine Open Space topicsLunch
13:30-14:15Open Space session 1
14:15-14:30Coffee breakBreak / Change
14:30-15:15Open Space session 2
15:15

-

15:30Summary of Open Space
15:30

-

15:35Grap a quick coffee
15:35-16:00Wrap Up and determine next steps

Topics

  • Do you have or expect to have a mobile application in your organization that could benefit from OIDC's support to "native apps"? Example scenario: "We have a mobile app that, upon successful authentication via LDAP, gives access to our internal VoIP system, allowing performing voice calls to the physical devices located at the different offices around the campus. Replacing this organization-only authentication with a federated one, visitors would be able to to call their hosts or any other administrative destination with no cost or hassle". 
  • What about server to server communication ? As easily (question) as we can build a OIDC federation we can build a OAuth2 federation which opens up some interesting new avenues.
  • One can imaging different federation operators taking different interest in the state of the federation. What kind of functionality would an involved federation operator need ?
  • What do others think about allowing 'anyone' to use their own APIs through the OIDC federation? ("Authorisation-Server-as-a-Service") (Arnout) 
  • It seems like OIDC significantly lowers the bar for integrating services with federations, which is for example noticed by the research community (at least in Australia (wink)). But what does this mean for federation policies, contracts, agreements, etc.? Will there be 2 separate federations with different technologies (SAML vs. OIDC) and different policy sets? (Arnout)
  • Attribute Release (Lukas)
  • Distributed Attributes (Roland) - Querying more then one endpoint
  • Discovery (Andreas)

Location

TNC17 Venue / Design Center Linz

...