1.
OpenID Connect
via WebIntents
@nov

2.
NASCAR Problem

3.
Discovery Issue

4.
Discovery on SmartPhone
• iOS
• Custom Schema Delegation
• Android
• android.content.Intent Class
• Windows Phone
• I’m a Mac user

5.
Discovery on SmartPhone
• iOS
• Custom Schema Delegation
• Android
• android.content.Intent Class
• Windows Phone
Discovery + Inter-app communication
• I’m a Mac user

6.
Discovery in HTML5
=> WebIntents

7.
delegatee.example.com

8.
delegatee.example.com
Register a delegatee for “share” action

9.
You share now.

10.
delegator.example.com

11.
delegator.example.com
Invoke “share” action delegation

12.
delegatee.example.com

13.
delegatee.example.com
Respond to delegator

14.
http://demos.webintents.org

15.
More details?
http://webintents.org

16.
OpenID Connect Discovery
via WebIntents

17.
End-User RP OP
Initiate
Discovery
Client Registration
Authorization Request
Code / Access Token / ID Token
UserInfo

18.
OP (delegatee)
$ https://connect-op.heroku.com
RP (delegator)
$ https://connect-rp.heroku.com

19.
What should be standardized?
Intent Action Value

20.
What should be standardized?
Response is not
a simple JSON document

21.
APPENDIX

22.
End-User RP OP
Initiate
Discovery
Client Registration
What should
Authorization Request be delegated??
Code / Access Token / ID Token
UserInfo

23.
In WebIntents,
no direct communication happens
between delegator and delegatee.
They won’t know each other.

24.
End-User RP OP
Initiate
Discovery
Client Registration
Authorization Request
Code / Access Token / ID Token
UserInfo