Transcript
Page 1: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

High  Value  Consumer  Transactions  

A  Relying  Party's  Perspective  

Page 2: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

Image by Andrew Horne

Page 3: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

Image by TheeErin

Page 4: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

So… what’s the context? �  Consumer  to  business    

�  Relying  Party  supporting  Identity  Federation  �  User  in  control  

�  High  value  transactions  �  Specifically  micro-­‐payments  

 

Page 5: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 6: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

Games  Platform  

Page 7: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

Purchase  Flow  

Page 8: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 9: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 10: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 11: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 12: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 13: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 14: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 15: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 16: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 17: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't
Page 18: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

What we learned

Complicated  

•  Customer  Service  o  finding  the  user's  

account  

•  Access  problems  due  to  issues  with  the  IdP  

•  Account  recovery  

Works  

•  Identity  Federation  for  Authentication  

•  Challenge  before  purchase  

Page 19: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

Relying Party trends •  Moving  away  from  identity  federation  for  authentication  

•  Using  social  login  for  attribute  collection  o  RP's  really  like  this  

•  Desire  to  control  the  entire  user  experience  

Page 20: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

What is driving these trends? •  User  Experience  Concerns  

o  Account  recovery  o  Forgot  IdP  /  Login  confusion  o  Merging  duplicate  accounts  o  Linking  multiple  federated  identities  together  o  Authentication  from  Mobile  apps  o  Delegation  o  User's  account  "blocked"  at  the  IdP  o  Customer  Service  Support  

Page 21: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

What is driving these trends? •  Business  Concerns  

o  Liability  and  dependence  on  external  party  (no  contracts)  o  IdP  policy  mismatch  with  RP  policies  (e.g.  data  use  policy)  

o  ROI  for  identity  federation  (or  lack  there  of)  o  Lack  of  knowledge/understanding  value  of  identity  federation  

•  Technical  Concerns  o  Legacy  system  already  dependent  on  username/password  o  Lack  of  a  successful  identity  standard  (or  maybe  too  many  

viable  ones)  o  Recyled  identifiers  

Page 22: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

Critical for the RP What  is  my  risk  in  supporting  Identity  Federation?  

•  How  many  customers  will  I  gain?  o  lower  barrier  to  entry  

•  How  many  customers  will  I  lose  if  something  goes  wrong?  

•  What  use  cases  do  I  need  to  handle  now  that  I'm  relying  on  another  entity?  

•  How  much  does  it  cost  to  implement  the  mitigation  flows  for  these  new  use  cases?  

Page 23: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

Easy solution •  Make  it  easy  for  every  RP  

to  be  their  own  IdP  

•  RP  controls  all  the  flows  

•  No  new  flows  to  deal  with  

•  Well  understood  user  experience  patterns  

Page 24: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

Problem Ignores  the  User  

•  Yet  another  site  asking  for  a  password  

•  Identifier/Password  management  nightmare  

•  Consumer  almost  guaranteed  to  be  compromised  

Page 25: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

Real solution •  Trust  frameworks  to  provide  some  assurances  between  RPs  

and  IdPs  

•  Industry  best  practices  for  the  new  flows  

•  IDaaS  provider  targeted  at  consumer  services  o  Easy  for  startups  to  leverage  o  Mitigations  for  unexpected  outages  o  Support  for  Federated  Identity  Providers  

Page 26: CIS13: Providing High Value Consumer Services as a Relying Party - IDaaS: What Works and What Doesn't

Questions & Maybe Answers

Contact  Information  

 [email protected] http://twitter.com/gffletch http://about.me/georgefletcher