Cutting Edge Mobile Development in the App Cloud
0 likes•286 views
The document outlines innovative web development practices on the Salesforce platform, highlighting forward-looking statements and associated risks. It discusses strategies to enhance user experiences across mobile and desktop through multi-org complexity management and secure authentication methods like OAuth. Additionally, it provides a basic overview of server route configurations and the integration of features like SSO and two-factor authentication.
![server.route( [
{
method: ['GET', 'POST'],
path: '/auth/oauth',
config: {
auth: {
strategy: 'oAuth'
},
handler: RouteHandlers.authRequest,
}
}
} );
Org & Heroku Config
Server Route Config](https://image.slidesharecdn.com/9r3tshlaska523bhlfja-signature-7873c75031ac31677418d06ca1135ba58cf1db5a062456d83a04778887726afe-poli-151012220117-lva1-app6892/85/Cutting-Edge-Mobile-Development-in-the-App-Cloud-11-320.jpg)
Cutting Edge Mobile Development in the App Cloud
- 1. Cutting edge web development on the Salesforce platform A Salesforce IT story Andy Bean Senior UI/UX Designer [email protected] Robert Birbeck Senior Software Engineer [email protected] Phi Tran Software Engineer [email protected]
- 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 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.
- 3. What is the future of the Intranet?
- 4. Architecture How do we obscure multi-org complexity and provide a best in class mobile and desktop experience? identity ● Workday ● ADP ● Etrade Canvas Google Search Appliance SSO 2 Factor authentication IP whitelisting signed request oauth
- 5. User Authentication - Signed Request identity Canvas signed request
- 6. User Authentication - Signed Request Concierge Signed Request flow Quick Simple Overview: ● User opens app in Salesforce1 ● Platform makes a POST to our server ● Server decodes payload POST
- 7. server.route( [ { method: 'POST', path: '/auth/signedrequest', config: { auth: { <--- Auth Handler strategy: 'signedRequest', payload: 'required' }, handler: RouteHandlers.authRequest <--- Route Handler } } } ); Org & Heroku Config Server Route Config
- 8. payload: function ( request, reply ) { … canvasRequest = decorder( request.payload.signed_request, process.env.clientSecret ); … return reply.continue( { credentials: canvasRequest } ); } Org & Heroku Config Server Route Config
- 9. authRequest: function ( request, reply ) { return reply.view( config.get( 'view' ), { canvasContext: request.auth.credentials } ); }, Org & Heroku Config Server Route Config
- 10. Setting up OAuth with Heroku OAuth Flow using hapi 1. Request Service 2. Redirect 5. Render View 3. Redirect URI w/ authorization code 4. POST to authorize endpoint
- 11. server.route( [ { method: ['GET', 'POST'], path: '/auth/oauth', config: { auth: { strategy: 'oAuth' }, handler: RouteHandlers.authRequest, } } } ); Org & Heroku Config Server Route Config
- 12. server.auth.strategy( 'oAuth', 'bell', { clientId: options.clientId, clientSecret: options.clientSecret, provider: { protocol: 'oauth2', auth: options.endpoint + '/services/oauth2/authorize', token: options.endpoint + '/services/oauth2/token', } } ); Org & Heroku Config Server Route Config
- 13. How do we make this work on the desktop? SSO + 2FA ● Setting up OAuth ● Extension ○ 2FA ○ SSO ● Light client code
- 15. Thank you