The document discusses seamless authentication processes for applications using the Force.com Canvas framework, focusing on enabling a user-friendly login experience across multiple applications. It details various authentication methods, including OAuth 2.0 and SAML integration, along with the management of user sessions across different Salesforce organizations. The presentation highlights best practices for implementing authentication and connecting multiple orgs with practical examples and demonstrations.

1. Seamless Authentication with
Force.com Canvas
Jay Hurst
Senior Product Manager, salesforce.com
@extraidea
Chris Jolley
Principal Developer, salesforce.com
@jolley

2. Safe Harbor
Safe harbor 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 andcustomer 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.

3. Jay Hurst
Senior Product Manager

4. Chris Jolley
Principal Developer

5. Navigating the Authentication Waters
• Providing a seamless login experience for users
canvas be difficult, especially when you have
multiple applications
– How many of you have multiple applications working with
your Salesforce organizations?
• Force.com Application, Multiple orgs, new applications
– How many have attempted to manage login with Salesforce
using Force.com Canvas?
• Federation Providers, SAML, One-off implementations
– How many of you would like to create a more seamless
authentication with your Canvas Application?

6. Canvas Authentication

7. Two Sides of Authentication
• Delivering a seamless login experience means managing two sides
– The Force.com Canvas Framework provides authentication into Salesforce
• Signed Request
• OAuth Webflow
– Loging into the Canvas App is up to the Canvas Develoepr
• No Authentication
• Username/Password
• SAML
• Other SSO Solution
• Together, the end user just gets access!

8. Canvas with OAuth Webflow
• Uses standard OAuth 2.0
– Salesforce loads the Canvas URL with a standard HTTP GET
• No authentication is passed
– Canvas app triggers the OAuth flow
• Using token passing or refresh token (if available)
– Canvas app sets the token in the Canvas JS Library, and calls getContext()
• This returns the context object to the Canvas App
• Requires a bit more management on the Canvas App end

9. Canvas with Signed Request
• Also uses OAuth 2.0, with a twist
– Token generation is done completely on the Salesforce side
– Salesforce does an HTTP POST to the Canvas URL
• Response to the POST is loaded into the Canvas iFrame
• First contact with Canvas App contains all of the context information
– Less “chatty”
– Preferred and default authentication

10. Demo
Signed Request Example

11. Authentication into the Canvas App
• Many ways to establish authentication into your app
– No authentication (open site)
– Have a username/password screen
– Have an established session in the browser
– Create your own SSO Solution
– Using a SAML flow

12. Demo
Seamless Authentication

13. Cross Org Visualforce
• By using SAML with your Canvas App, your can link VF pages between orgs
– You must have named users in both orgs
– You must use MyDomain feature (to avoid session conflicts)
– Org you are showing the VF page in, is the Identity Provider
– Org hosting the VF is the Service Provider
– Canvas provides the authentication to the source org, so that it can call into the hosting org
• Provides a way to begin to stich your Orgs together

14. Cross Org VF - Setup
• Two orgs: Identity Provider (outer frame), Service Provider (inner frame hosting VF)
• Identity Provider org provides the certificate for SAML validation
– Service Provider Org consumes the cert
• IdP Org provides creates a connected app used to connect to the SP org
– This app also contains the Canvas information
• SP Org sets up the VF pag
• With this setup:
– User logs into IdP
– User Opens Canvas App that points to SP VF Page
– SAML SSO happens and logs user into SP seamlessly and show VF page
– User (or VF page on SP) establishes context to IdP so it can use the Canvas API

15. Demo
Canvas SAML Setup

16. Demo
Cross Org Chatter

17. Wrapup/What Have We Learned?
• Today we learned how to manage authentication with Force.com Canvas
– How doe Force.com Provide authentication into salesforce.com
– How can you login to your Canvas App
– How can you seamlessly login to both sides
• We also learned how to connect two orgs with Force.com Canvas
– How do you prepare the orgs
– How do we link the orgs together
– What does a VF implementation look like

18. Q&A