View
6.450
Download
3
Category
Preview:
DESCRIPTION
Single Sign-On gives Salesforce users huge gains in usability and security, but the ins-and-outs of how it works and where to start can be complex for admins and developers. Join us as we go over the details and best practices that will help you take full advantage of single sign-on. We'll give you an overview of the integration options (SAML, Delegated Authentication, and Oauth ) as well as tips on advanced topics like bookmarks, deeplinks, mobile devices, and API federation. Need more? We'll also do a live configuration demo of single sign-on. See for yourself just how easy it is!
Citation preview
Single Sign-On and Federation with Salesforce
Developers
Chuck Mortimore: Salesforce.com@cmort
Safe HarborSafe 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 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, 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 intellectual property and other litigation, risks associated with 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 ended January 31, 2010. This documents and others 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 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.
Why Single Sign-On?
Login with your enterprise credentials
Leverage existing authentication investments
Improve usability for your users
Reduce support costs
Improve adoption rates
Maintain control of credentials with your policies
Reduce risk with a single place to shut down accounts
What is SAML?
Security Assertion Markup Language
OASIS Standard used for Single Sign-On
Strong commercial and open source support
Authentication interface is hosted by customer
① User requests a secure resource
② Salesforce.com redirects to Customer IDP
③ Customer authenticates user
④ User returns to Salesforce.com with SAML
and granted session
* If you’re logged into the DreamForce org, you’ve used SAML!
What is Delegated Authentication?
SOAP based protocol for “Single Login”
Only implemented by Salesforce
Minimal commercial support
Salesforce hosts the authentication interface
① User sends credentials to Salesforce
② Salesforce sends credentials to Customer
③ Customer authenticates user and replies “true”
④ User is granted session to Salesforce
Choosing a Protocol
SAML provides the best commercial support
SAML provides re-use across other Cloud services
Delegated Auth is still best for Mobile & Desktop
Not mutually exclusive: Customers can and do use both
Configuring SAML
Getting Started with SAML
Setup > Security Controls > Single Sign-On Settings
You’ll need an “issuer” and certificate from your IDP
Choose your User ID Type– Salesforce.com username ( globally unique )
– FederationID ( unique to an org )
Choose a User ID location– SAML Subject or an arbitrary SAML Attributes
Configuring Delegated Authentication
Getting Started with Delegated Authentication
Has to be enabled via Support
Implement/deploy your endpoint
Enable your Delegated Authentication Endpoint
Configure the User’s profile
REQUEST
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope> <soapenv:Body> <Authenticate> <username>sampleuser@sample.org</username> <password>password</password> <sourceIp>1.2.3.4</sourceIp> </Authenticate> </soapenv:Body></soapenv:Envelope>
RESPONSE
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope> <soapenv:Body> <AuthenticateResponse> <Authenticated>true</Authenticated> </AuthenticateResponse> </soapenv:Body></soapenv:Envelope>
Advanced Topics
Deep-linking and Bookmarking
Users share links, and bookmark resources
Historically difficult given Salesforce URLs – Example: https://na1.salesforce.com
Leverage a new features called ‘My Domain’– Example: https://customer.my.salesforce.com
Allows a custom URL to identify your Org
Deeplinking, bookmarks, emails, and sharing all as
simple as Admin configuration
‘My Domain’ Demo
What about Native Clients?
Mobile and products not yet able to participate in SAML
Transitioning clients to OAuth so authentication is
happening in a browser
Integrating SAML and OAuth flows via My Domain
Expect first clients early next year
Native Client Demo
Got Orgs?
Many customers are managing multiple Salesforce orgs
Winter 11 enables multi-org web SSO with SAML
Does not unify API or Mobile/Desktop access
Must use ‘My Domain’ and custom entity ID
Customer acts as a ‘Hub’ - Orgs are ‘Spokes’
Multi-Org Demo
API Federation
Customers want similar capabilities for API Access
Salesforce has innovated a SAML / Oauth flow along
with Ping Identity
Allows reuse of your existing software and established
trust
The exact same federation you’ve established for the
web now works with the API
API Federation Demo
Salesforce.com as an Identity Provider
Salesforce Orgs are now SAML Identity Providers
Initially limited to simply asserting a Salesforce subject
Foundation for integration projects or tying together
multiple clouds
Salesforce Identity Provider Demo
Questions?Implementation Guide
https://na1.salesforce.com/help/doc/en/salesforce_single_sign_on.pdf
SAML http://wiki.developerforce.com/index.php/Single_Sign-On_with_SAML_on_Force.com
Delegated Authenticationhttp://wiki.developerforce.com/index.php/How_to_Implement_Single_Sign-
On_with_Force.com
Single Sign-On and Federation with Salesforce
D I S C O V E R
Visit the Developer Training and Support Booth in Force.com Zone
Discover
Developer
Learning Paths
Developer training, certification and support resources
S U C C E S SFind us in the Partner Demo Area of
Force.com Zone 2nd Floor Moscone West
that help you achieve
Learn about Developer
Certifications
Remember. . .
Check Chatter for additional session information
Get your developer Workbooks and Cheat Sheets in
the Force.com Zone
Visit for more information related
to this topicDon’t forget the survey!
How Could Dreamforce Be Better? Tell Us!
Log in to the Dreamforce app to submit
surveys for the sessions you attendedUse the
Dreamforce Mobile app to submit
surveysEvery session survey you submit is
a chance to win an iPod nano!
OR
Recommended