Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The State of Auth - Boulder Ruby Oct. 2011

The State of Auth - Boulder Ruby Oct. 2011

Wherein @ubermajestix describes various auth frameworks and asks whether or not you should roll your own auth solution.

Avatar for ubermajestix

ubermajestix

October 19, 2011
Tweet

More Decks by ubermajestix

Other Decks in Technology

Transcript

  1. THE STATE OF AUTH Boulder Ruby Group, October 2011 tyler

    montgomery @ubermajestix Wednesday, October 19, 2011
  2. Hi, I’m Tyler Ruby and Rails ~ 5 Years Everlater

    formerly of CollectiveIntellect Wednesday, October 19, 2011
  3. Some stats: “75% of attacks are at the web application

    layer” - The Gartner Group Wednesday, October 19, 2011
  4. Some more stats: “300 audited sites 97% are vulnerable to

    attack” - The Gartner Group Wednesday, October 19, 2011
  5. What’s out there? (Fill in pros and cons if I

    miss any) Wednesday, October 19, 2011
  6. Warden :) Rack Middleware to manage the session. Scopes! oooh

    neat. Easy to extend. Wednesday, October 19, 2011
  7. Warden :( Setup, in my experience, was a little difficult.

    Sinatra-Warden project is dead. No helpers. You're going to hack it anyway. Wednesday, October 19, 2011
  8. Devise :( “a complete MVC solution based on Rails engines”

    You're going to hack it anyway. Wednesday, October 19, 2011
  9. Authlogic :( Lots of options to cover every use case

    you don’t have You're going to hack it anyway. Wednesday, October 19, 2011
  10. Sorcery :) Modular Config in one place You do the

    MVC Lots of docs Wednesday, October 19, 2011
  11. Sorcery :( Only at 0.7.0 You're going to hack it

    anyway. Wednesday, October 19, 2011
  12. Using a gem to help is great, but you're at

    someone else's mercy. Wednesday, October 19, 2011
  13. A 3rd party lib will not meet your requirements nor

    cover all of your edge cases... rails generate scaffold... done. Wednesday, October 19, 2011
  14. I thought Authlogic couldn’t but there was some weird dsl

    to handle it Wednesday, October 19, 2011
  15. The whole point is to have a secure, maintainable and

    easy to use system. Wednesday, October 19, 2011
  16. If you’re going to have to maintain something, why not

    maintain your own code? Wednesday, October 19, 2011
  17. Writing your own auth system FORCES YOU to understand the

    problem. Wednesday, October 19, 2011
  18. Auth controller - everything's at /auth signup, activation, login, logout,

    forgot_password, reset_password sudo, unsudo Wednesday, October 19, 2011
  19. All apps get middleware to deal with the session and

    redirection. like Warden Wednesday, October 19, 2011
  20. Wins: each app has almost no setup login happens in

    one place Wednesday, October 19, 2011
  21. Not wins: users randomly getting logged in as each other.

    doesn’t conform to a standard (like oauth) Wednesday, October 19, 2011
  22. Github implemented oauth You can use it. “Sign in with

    github” Wednesday, October 19, 2011