Seth Vargo 11/4/2013

Authorizers, Extractors, and Policy objects

Read Original

The article discusses a Rails 4 project's challenge with authorization frameworks and multi-provider OAuth. It critiques common patterns that lead to bloated models and introduces a cleaner, object-oriented solution using Policy objects and Extractors to handle user data from different OAuth providers (like GitHub, Twitter) in a DRY and maintainable way.

Authorizers, Extractors, and Policy objects

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week