…3.1,, , , , OmniAuth, and .
Moxy - " Programmable mock proxy", that is, a server that lets you tell it what to return for testing purposes.
Felix's - Lots of material here, including a beginner's guide and a style guide. Guide
snowday - result formatter for featuring snowmen.
Jenx - monitor for with integration. …
Example Rails 3.1.1 App using and OmniAuth 1.0
With OmniAuth 1.0 out just last week, it's great to seehas updated his popular 3.1 example app to the latest and greatest. If you want to see how to bring Mongoid and OmniAuth together with Rails 3.1, this is a great place to start.
RBzip2: A Pure Ruby Implementation of the bzip2 ( )Compression Algorithm
Sinatra-Static: Turn a into a Site
…thoughtbot/clearance-twitter was alibrary that played nicely with Clearance. Omniauth is the bomb and should be used instead.
Some projects were forks where we needed to add additional functionality or fix bugs. We're deleting those repos and mentioning them here with alternatives in case you were ever using one of our forks.
Ancestry allows the records of a model to be organised as a tree structure (or …
…integration test_mode that makes testing OAuth logins less sucky than it's ever been before. Fortunately for us, and OmniAuth go together like giant chocholate swamp rat and creamy peanut butter. It pretty much works right out of the box.integration testing to be easy, you'll want to make sure you're using the OmniAuth 0.2.0 or later. Among it's many fine features is a new
To demonstrate, let's add a nice little integration auth helper …
Musings from - OmniAuth based login via Cucumber
This morning we needed to write ascenario to test that a user could log into the system using .
Timeago is aplugin that makes it easy to support automatically updating fuzzy timestamps (e.g. "4 minutes ago").
A Few ObjectId Tricks // MongoTips byNunemaker …
Kevin Ball shows how the traditional model of username/password authentication is dying, and how Omniauth makes it all rainbows and sunshine going forward.
Step One: OmniAuth Up and Running
First we'll need to include OmniAuth in our Gemfile . Just add it like so: gem 'omniauth'
Next, we should configure OmniAuth for our Google Apps login. Note that you can add this even if you're already using a different Google Apps strategy for OmniAuth. Create the file config/initializers/omniauth.rb and put this in it: Rails.application.config.middleware.use OmniAuth::Builder do |b| provider :google_apps, :domain => …
Our Michael Bleigh , was hard at work this year writing a library to simplify all of the different logging-in strategies that today's web applications try to leverage. Whether it's , , or even , the OmniAuth library handles it all with ease. The library was used heavily in the 2010 competition. Here's what Rumble had to say about …of ,
…internals, because it is already tested in gem's tests, so we go to the next step: testing the OmniAuth callback.
Faraday internally to connect to the provider. With , we can configure a test adapter and stub calls to return what we want.OmniAuth callbacks is in general cumbersome but for providers it is a bit easier as it uses
The OmniAuth strategy provides an entry point to the Faraday connection, but we don't have an access to the strategy …
Interesting tidbits from around the web (December 16th):
sferik/rails_admin - GitHub - a 3 admin interface (think MerbAdmin or ) built as a rails engine
Multiple - with , Omniauth and On « Josh Software - Where is an Art! shows how to stand up a couple rails apps that share single sign on with devise and omniauth