The document discusses OAuth and social authentication. It begins with a statement under the Private Securities Litigation Reform Act noting that any forward-looking statements could differ materially from expressed results due to uncertainties. It then lists various risks and uncertainties including developing new functionality, possible fluctuations in operating results, interruptions in web hosting, security breaches, litigation outcomes, and more. The document also notes that any unreleased services mentioned may not be delivered or could be delayed.

1. OAuth & Social Authentication
July 26th
2016

2. Statement under the Private Securities Litigation Reform Act of 1995:
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of
the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking
statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service
availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future
operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of
our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service,
new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions
or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and
acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and
manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization
and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our
annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and
others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be
delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available.
Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
Forward-Looking Statement

3. Go Social!
@salesforcedevs / #forcewebinar
Salesforce Developers
Salesforce Developers
Salesforce Developers
This webinar is being recorded!
The video will be posted to YouTube and the
webinar recap page (same URL as registration).

4. Agenda
• SSO
• OAuth
• Social Sign On
• Demo / Examples
• Resources
• Q&A

5. Prerequisites
• Good understanding of Platform Concepts
• Basic understanding of Authentication.

6. SSO

7. Single Sign On - Definition
• Reduce Administration Costs
• Existing Investment
• Increased Security
• User Adoption

8. Types of SSO
• SAML Authentication
• Delegated Authentication
• OAuth

9. SSO Continued
SSO challenges the architects and integration experts to perhaps
build the most complex integrations of their careers

10. OAuth

11. What is OAuth

12. OAuth Terminology
• Resource Server - this is the web-server you are trying to access
information on.
• Client - this is how the user is interacting with the Resource
Server. This could be a browser-based web app, a native mobile
app, a desktop app, a server-side app.
• Authorization Server - this is the server that owns the user
identities and credentials. It's who the user actually authenticates
and authorizes with.

13. OAuth Flow

14. Social Authentication

15. Social Authentication
• Authenticate using any Social Profile

16. Social Authentication Uses
• One click
• One Username/Password
• More secure
• More Data Quality
• Reliable Sources
• Automation

17. Social Authentication Types
• Open ID Connect
• Janrain (Custom)
• Microsoft ACS
• Custom
• Facebook
• LinkedIn
• Google

18. Demo

19. Social Sign On
• Set Up a Facebook application
• Define a Facebook Auth. Provider in your salesforce
organization
• Update your Facebook application with the callback URL
generated by Salesforce
• Test Connection with Facebook
• Create a registration handler
• Single Sign-on with Facebook

20. Open ID Connect
• Delegate User
Authentication
• Based on OAuth 2.0
• JSON Based
• More Secure

21. Social Sign On
• Use Open ID Connect
• Point to a Connected App in
Salesforce
• Build the Registration Handler for JIT
Provisioning
• Setup Community Login Page.

22. Recap
• Define what is SSO
• Types of SSO
• Definition of Oauth and Oauth Flows
• Types of Social Sign On in Salesforce
• Setting Up Auth Providers and connecting using various Auth Providers

23. Resources
• https://developer.salesforce.com/blogs/developer-relations/2014/06/how-to-provision-
salesforce-communities-users.html
• https://developer.salesforce.com/page/Social-Sign-On
• https://www.youtube.com/watch?v=T1fpulzHYcs

25. Got Questions?
developer.salesforce.com/forums/

26. Your feedback is crucial to the success
of our webinar programs. Thank you!
Q&A

27. Thank You
Try Trailhead: trailhead.salesforce.com
Join the conversation: @salesforcedevs