Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Uma webinar 2014 03-20

1,265 views

Published on

Kantara Initiative's UMA Work Group published revision 9 of its OAuth-based protocol on March 6 to solve a broad range of "access management 2.0" challenges, and will shortly begin interoperability testing. On Thursday, March 20, at 8am Pacific, the UMA Work Group conducted a free public webinar sponsored by Kantara board member CA Technologies to discuss UMA's benefits for enterprises. This is a capture of the slides from the webinar. The video can be found at http://bit.ly/1iEs30O

Published in: Technology
  • Be the first to comment

Uma webinar 2014 03-20

  1. 1. Access Management 2.0: UMA for the Enterprise @UMAWG #UMAam20 for questions 20 March 2014 tinyurl.com/umawg for slides, recording, and more 1
  2. 2. Agenda •  The realities and challenges of modern access control (CA) •  “UMA for the Enterprise 101” •  Enterprise UMA case study and demo (Gluu) •  What vendors are saying and doing about UMA •  Q&A 2 Thanks to CA Technologies for sponsoring this webinar! Thanks to Kantara for supporting the UMA work! Thanks to our additional webinar participants!
  3. 3. The realities and challenges of modern access control 3 Further reading: tinyurl.com/umaam20
  4. 4. 4         Copyright © 2014 CA. All rights reserved. UMA  Con(nues  The  Shi0  In  Iden(ty  Management   That  Began  With  OAuth   The Traditional Enterprise The 21st Century Enterprise This is the secret to achieving scale and agile federation
  5. 5. “UMA for the Enterprise 101” 5 Further reading: tinyurl.com/umafaq
  6. 6. OAuth is a three-entity protocol for securing API calls in a user context 6 Source:  The  OAuth  2.0  Authoriza4on  Framework,  h;p://tools.ie@.org/html/rfc6749   End-user resource owner gets redirected to AS to log in and consent to access token issuance AS and RS are typically in the same domain and communicate in a proprietary way
  7. 7. UMA’s original goal: apply privacy- by-design to OAuth data sharing 7 Standardized APIs for privacy and “selective sharing” Outsources protection to a centralized “digital footprint control console” The “user” in User-Managed Access (UMA) Some guy not accounted for in OAuth… Further reading: tinyurl.com/umapbd
  8. 8. Emergent UMA properties: flexible, modern, claims-based authorization 8 Source:  XACMLinfo.org,  h;p://xacmlinfo.org/2011/10/30/xacml-­‐reference-­‐architecture/   consumes authz data associated with token native or a client of offboard source(s), in any language(s) claims gathered through user interaction and/or consuming ID tokens UMA and XACML can coexist nicely
  9. 9. The RS exposes whatever value-add API it wants, protected by an AS 9 App-specific API UMA-enabled client RPTrequesting party token
  10. 10. The AS exposes an UMA- standardized protection API to the RS 10 ProtectionAPI Protectionclient PAT protection API token includes resource registration API and token introspection API
  11. 11. The AS exposes an UMA- standardized authorization API to the client 11 Authorization API Authorization client AAT authorization API token supports OpenID Connect-based claims- gathering for authz UMA, SAML, and OpenID Connect can coexist nicely
  12. 12. Key use cases •  Managing personal data store access •  E-transcript sharing •  Patient-centric health data access •  …and enterprise access management 2.0 12 Source:  MIT  Consor4um  for  Kerberos  and  Internet  Trust,  h;ps://kit.mit.edu  
  13. 13. AM1.0 vs AM2.0 •  Complex and feature-rich •  Usually proprietary •  Mobile/API-unfriendly •  Brittle deployment architecture •  Not agnostic to authn method •  Hard to source distributed policies •  Usually coarse-grained •  RESTful and simpler •  Standard interop baseline •  Mobile/API-friendly •  Just call authz endpoints vs. deploying an agent •  Agnostic to authn method and federation usage •  Flexible in policy expression and sourcing •  Leverages API’s “scope- grained authorization” 13
  14. 14. Enterprise UMA case study 14
  15. 15. What vendors are saying and doing about UMA 15 Further  reading:   4nyurl.com/uma1iop  
  16. 16. NuveAM by Cloud Identity •  UMA-compliant AS: –  Access control to Web data –  API security and management –  Real-time monitoring and audit •  Use cases: Securing Personal Data Services (PDS) and access management 2.0 (API security) •  Uses open standards, including UMA, OAuth 2.0, OpenID Connect, and SAML 2.0 •  Open source frameworks: Java and Python •  Support for mobile (Android) •  Integrates with Identity Management and Identity Federation http://www.cloudidentity.co.uk/products/nuveam 16
  17. 17. NuveAM by Cloud Identity 17
  18. 18. NuveAM for the enterprises 18 •  Management of resources, APIs, permissions, and access control policies •  Access control on demand •  Detailed audit information •  Application management: resource servers and clients (with NuveLogin) •  Integration with identity management •  Integration with identity federation and SSO
  19. 19. NuveAM for the enterprises 19
  20. 20. NuveAM for the enterprises 20
  21. 21. Next steps 21
  22. 22. Next steps for the WG…and you •  Get involved! –  Become an “UMAnitarian” (it’s free) –  Participate in the interop and our implementation discussions –  Follow and engage with @UMAWG on Twitter •  Current work: –  Technical: claim profiling to allow claim-gathering using SAML, OpenID Connect, LDAP… –  Business: Binding Obligations spec to tie “terms of authorization” to multi-party state changes •  Stay tuned for another webinar in Q2 22 Join  at:   4nyurl.com/umawg  
  23. 23. Questions? Thank you! @UMAWG #UMAam20 for questions 20 March 2014 tinyurl.com/umawg for slides, recording, and more 23

×