Building an SSO platform in php (Zendcon 2010)
27 likes11,161 views
A presentation explaining how to build Single Sign On functionality in PHP using standards such as OpenID, OAuth and SAML. Delivered on November 4, 2010 at Zendcon in Santa Clara
More Related Content
What's hot (20)
Similar to Building an SSO platform in php (Zendcon 2010) (20)
More from Ivo Jansch (20)
Recently uploaded (20)
Building an SSO platform in php (Zendcon 2010)
- 1. Building an SSO platform Ivo Jansch - Egeniq November 4, 2010 - Zendcon
- 4. Single Sign On Why do we need it?
- 5. We use many applications Your other corporate application Your corporate application
- 6. Across devices and locations Your other corporate application Your corporate application
- 7. A quick poll
- 8. Level 0 - One Password To Rule Them All
- 9. 1 password to rule them all Your other corporate application Your corporate application
- 10. Level 1 - Shared Identity Using a single authentication backend for apps
- 12. Level 2 - OpenID Using OpenID for external Identity Management
- 16. Delegate to OpenID provider
- 18. Caveats OpenID providers hesitant to be OpenID consumers No trust establishment between consumer and provider
- 19. Level 3 - OAuth Using OAuth for external IDM and authorization
- 21. Landing adjusted for OAuth
- 23. Delegate auth to Twitter
- 25. Level 4 - SAML Creating our own Identity Provider
- 26. SAML Security Assertion Markup Language XML standard by OASIS Assertions contain: Proof of Identity Attributes Supports XML signatures and encryption
- 30. IDP Auth Source Configuration
- 33. IDP Virtual Host Apache Config
- 34. Testing the IDP
- 36. SP Auth Source Configuration
- 38. Back to our landing page
- 39. Delegate auth to the IDP
- 40. Integrating 3d party apps Simplesamlphp is easy to integrate
- 43. SugarCRM Plugin: didn’t work Problem: auth structure Solution: hacking the source Options: Contact me if you need to get SugarCRM to do SSO :-) Wait for SugarCRM 6.1, it contains a working SAML plugin (/via @smalyshev)
- 44. Google Apps Requires Premier or Education Edition Configure SAML endpoint => Done! Docs: http://code.google.com/googleapps/domain/sso/ saml_reference_implementation.html
- 45. Google Apps
- 46. Making apps SSO ready Application Logged in? Auth Plugin Yes Show Site Login Form Authenticate Start No
- 47. Making apps SSO ready Application Logged in? Auth Plugin Yes Show Site Login Form Authenticate Start No
- 48. Making apps SSO ready Application Logged in? Auth Plugin Yes Show Site Login Form Authenticate Start No
- 49. Making apps SSO ready Application Logged in? Auth Plugin Authenticate Start No Login Form Show Site Login Form Yes
- 50. Level 5 - Federation Dealing with multiple Identity Providers
- 54. The Future
- 55. The Future
- 56. Conclusion What should you take away from this talk?
- 57. In your next project... You will NOT create more userids !! You WILL use standard protocols !!
- 58. Thank You [email protected] http://www.egeniq.com @ijansch @egeniq Please leave feedback at: http://joind.in/2282
- 59. Credits Pictures used in this presentation are creative commons attribution licensed pictures. Here are the owners and the URLS where the originals can be found: ‘Multiple Padlock Farm Gate’ by Mike Baird - http://www.flickr.com/photos/mikebaird/2354116406/ ‘Love Locks’ by James Manners - http://www.flickr.com/photos/jmanners/443421045/ ‘Seguridad’ by Juan J. Martinez - http://www.flickr.com/photos/reidrac/4696900602/ ‘Hotel Keys by Henri Bergius - http://www.flickr.com/photos/bergie/3468886680/ ‘OAuth Shiny’ by Chris Messina - http://www.flickr.com/photos/factoryjoe/3343062926/ ‘Take a number please’ by Andres Rueda - http://www.flickr.com/photos/andresrueda/3259487071/ ’38/365 Puzzled’ by Mykl Roventine - http://www.flickr.com/photos/myklroventine/3261364899/ ‘Visiting Portage’ by Jeremy Bronson - http://www.flickr.com/photos/jbrons/4444017497/ ‘_dsc8037’ by Sergey Vladimirov - http://www.flickr.com/photos/vlsergey/4138735474/ Application logo’s and other icons have been used under the assumption that use of them in this context is considered fair use.