adapting oauth to the enterprise

17
Session ID: Session Classification: Chuck Mortimore salesforce.com IAM-F42A Intermediate ADAPTING OAUTH TO THE ENTERPRISE Pat Patterson salesforce.com

Upload: pat-patterson

Post on 10-May-2015

2.178 views

Category:

Technology


0 download

DESCRIPTION

OAuth has won wide acceptance in the web consumer space, with providers such as Facebook, Google and Twitter rolling the technology out to millions of users. What about the enterprise? In this session, we will reveal how salesforce.com has deployed OAuth to secure API access for thousands of enterprise customers, putting them firmly in control of access to their business data.

TRANSCRIPT

Page 1: Adapting OAuth to the Enterprise

Session ID:

Session Classification:

Chuck Mortimoresalesforce.com

IAM-F42A

Intermediate

ADAPTING OAUTH TO THE ENTERPRISE

Pat Pattersonsalesforce.com

Page 2: Adapting OAuth to the Enterprise

THE CONSUMER EXPERIENCE

Page 3: Adapting OAuth to the Enterprise

CONSUMER EXPERIENCE

Page 4: Adapting OAuth to the Enterprise

CONSUMER EXPERIENCE

Page 5: Adapting OAuth to the Enterprise

CONSUMER EXPERIENCE

Page 6: Adapting OAuth to the Enterprise

CONSUMER EXPERIENCE

Page 7: Adapting OAuth to the Enterprise

STRAIGHT OAUTH

Page 8: Adapting OAuth to the Enterprise

► Device opened a browser with authorization URL

► Tokens returned on URL behind # fragment – instrumented browser is monitoring and parses URL

WHAT JUST HAPPENED?

Page 9: Adapting OAuth to the Enterprise

► Simple Developer Experience► Approachable without massive investment

► Mobile Optimized► This is where your business processes are going

► Broad platform applicability► It’s just HTTP

► Adaptive Authentication► Allows us to leverage the web

► Context► Adds Application as an actor

WHY WE LOVE OAUTH

Page 10: Adapting OAuth to the Enterprise

► Passwords► What about assertions, token services, and federation?

► Consumer Authorization► Who has jurisdiction over enterprise resources?

► Server to Server ► What if I don’t have a “user”?

WHAT THE ENTERPRISE DOESN’T LOVE

Page 11: Adapting OAuth to the Enterprise

► 1 - Device opens browser with Authorize URL► 2 - Service Provider sends SAML Request to IDP► 3 - User Authenticates ► 4 - Identity Provider sends SAML Response to SP► 5 - OAuth request is Authorized ► 6 - Authorization Service responds with code or Token

Response

MOBILE FEDERATION

Page 12: Adapting OAuth to the Enterprise

OAUTH + SAML

Page 13: Adapting OAuth to the Enterprise

► Admin “installs” app

► App Uses any OAuth Flow

► User Authorization is determined via Admin settings

► Optional Policy Enforcement

ADMIN AUTHORIZATION

Page 14: Adapting OAuth to the Enterprise

► RESTful STS Pattern► Apps can exchange Credentials or Assertions for API

tokens► Enables API Federation, and password-less Cloud

► Username / Password Flow► Simple, but uses passwords

► Web SSO Assertion Flow► Reuse SAML SSO and existing Trust

► SAML/JWT Assertion Flow► Cert and Trust Specific to the App

SERVER TO SERVER OAUTH

Page 15: Adapting OAuth to the Enterprise

SUMMARY

Page 16: Adapting OAuth to the Enterprise

► OAuth 2.0 is not just for consumer apps► Can be composed with federation protocols – SAML etc► Can be brought under enterprise admin control► Can be used for Server-to-Server integration

SUMMARY

Page 17: Adapting OAuth to the Enterprise

Q & A

Chuck [email protected]

Pat [email protected]