Advanced Platform Series - OAuth and Social Authentication

715 views

Published on

Learn the benefits of using social authentication to log into your Salesforce org or community. During this session, you’ll become familiar with authentication nomenclature and understand the differences between being an identity provider vs. service provider. We’ll also show the mechanics to allow social sign-on for registration and user creation using Apex.

Published in: Software
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
715
On SlideShare
0
From Embeds
0
Number of Embeds
408
Actions
Shares
0
Downloads
42
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Good Morning, Good Afternoon & Good Evening. Thank you all for joining me today for another advanced webinar series. Today we will be learning about Oauth and Social Authentication
  • Single sign-on is a process that allows network users to access all authorized network resources without having to log in separately to each resource. Single sign-on allows you to validate usernames and passwords against your corporate user database or other client application rather than having separate user passwords managed by Salesforce.
  • Delegated Authentication (DA) is a proprietary technology that allows users to enter their existing Windows password.Salesforce does not validate a user’s password but rather makes a Web Service call to your organization to establishauthentication credentials for the user
    Federation using SAML is a standards-based Single Sign-On solution. Like DA, it does not validate the user’s actualpassword on the Force.com platform. Instead the platform receives a SAML assertion in an HTTP POST request. TheSAML assertion has a limited validity period, contains a unique identifier, and is digitally signed. If the assertion is stillwithin its validity period, has an identifier that has not been used before, and has a valid signature from a trusted identityprovider, the user is granted access to the application. If the assertion fails validation for any reason, the user is informedthat their credentials are invalid.
  • Resource Owner : An entity capable of granting access to a protected resource. Most of the time, it's an end-user.
    Client : An application making protected resource requests on behalf of the resource owner and with its authorization. It can be a server-based, mobile (native) or a desktop application.
    Resource Server : The server hosting the protected resources, capable of accepting and responding to protected resource requests.
    Authorization Server : The server issuing access grants/tokens to the client after successfully authenticating the resource owner and obtaining authorization.
  • http://www1.janrain.com/rs/janrain/images/Industry-Research-Value-of-Social-Login-2013.pdf
  • http://www1.janrain.com/rs/janrain/images/Industry-Research-Value-of-Social-Login-2013.pdf
  • If time permits, show the Monitoring pages
  • OpenID Connect is an interoperable authentication protocol based on the OAuth 2.0 family of specifications. It uses straightforward REST/JSON message flows with a design goal of "making simple things simple and complicated things possible".
    Although the standard was ratified only recently, in February 2014, it has already seen widespread adoption, notably byGoogle and Microsoft as well as salesforce.com.
    Salesforce Identity uses OpenID Connect to authenticate users across orgs and providers, reducing the number of passwords and other credentials that users have to manage.
  • Advanced Platform Series - OAuth and Social Authentication

    1. 1. OAuth & Social Authentication July 26th 2016
    2. 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. 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. 4. Agenda • SSO • OAuth • Social Sign On • Demo / Examples • Resources • Q&A
    5. 5. Prerequisites • Good understanding of Platform Concepts • Basic understanding of Authentication.
    6. 6. SSO
    7. 7. Single Sign On - Definition • Reduce Administration Costs • Existing Investment • Increased Security • User Adoption
    8. 8. Types of SSO • SAML Authentication • Delegated Authentication • OAuth
    9. 9. SSO Continued SSO challenges the architects and integration experts to perhaps build the most complex integrations of their careers
    10. 10. OAuth
    11. 11. What is OAuth
    12. 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. 13. OAuth Flow
    14. 14. Social Authentication
    15. 15. Social Authentication • Authenticate using any Social Profile
    16. 16. Social Authentication Uses • One click • One Username/Password • More secure • More Data Quality • Reliable Sources • Automation
    17. 17. Social Authentication Types • Open ID Connect • Janrain (Custom) • Microsoft ACS • Custom • Facebook • LinkedIn • Google
    18. 18. Demo
    19. 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. 20. Open ID Connect • Delegate User Authentication • Based on OAuth 2.0 • JSON Based • More Secure
    21. 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. 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. 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
    24. 24. Got Questions? developer.salesforce.com/forums/
    25. 25. Your feedback is crucial to the success of our webinar programs. Thank you! Q&A
    26. 26. Thank You Try Trailhead: trailhead.salesforce.com Join the conversation: @salesforcedevs

    ×