This document discusses internet requirements for personal clouds, including standards for authentication, authorization, and data federation. It compares OpenID Connect to OpenID 2.0, noting improvements in OpenID Connect like support for mobile clients, email identifiers, and endpoints for user claims. UMA is mentioned for authorization. Graph models are discussed for representing data structures for federation, with the OpenID Graph model using nodes and arcs to represent statements about subjects, predicates, and objects.

1. Internet Requirements for
Personal Clouds
8/7/2013

2. What we need…
• Standards for:
–Authentication
–Authorization
–Data Federation

3. OpenID Connect vs. OpenID 2.0
• Support for native / mobile client applications
• Identifiers using e-mail address format
• UserInfo endpoint for simple claims /
attributes about person
• Uses JSON/REST not XML
• Support for encryption and higher LOAs
• Support for logout
• Bootstrapable: Discovery / Client Registration
For more info : http://www.gluu.co/.gz3v

5. UMA for Authorization

6. How to central express policies in OX

7. Data Structures for Federation ?
tree
table
flat
graph

8. Why do we need graphs?

9. OpenID Graph Model
Point = Single node
Arc = How two points are related
GRAPH = Collection of XDI Statements
OpenID Graph
has three kinds of
arcs: contextual,
relational and literal

10. Statement
• subject/predicate/object
• mike@gluu.org/daughter/zia@kinzy.com
• mike@gluu.org/age/(data:,43)
• Use “slashes” when you get to a literal or
relational arc

11. OpenID Graph Operations
• $get
• $add
• $mod
• $del