Implementing Single Sign-on Using Rails, Oauth2 and Wordpress as an Oauth Provider.
Object Partners
In this post I will explain how to configure Rails to perform single sign-on authentication using Oauth2 and your hosted Wordpress site as an authentication provider.
I’ve worked on a few projects lately where there was a need to integrate a Rails site with an existing Wordpress site in a Single Sign On fashion but without authenticating against a central auth store or use of an SSO appliance. It is very easy to turn an existing Wordpress installation into an OAuth provider and skip the hassle of maintaining a central authentication store or a conversion effort for users already using your Wordpress blog.
Upload ouath2-complete to the /wp-content/plugins/ directory or use the built in plugin install by WordPress
Activate the plugin through the ‘Plugins’ menu in WordPress
Click ‘Settings’ and then ‘permalinks’. Then simply click ‘Save Changes’ to flush the rewrite rules so that OAuth2 Provider permalinks are generated for the site.
Last you must configure an Oauth2 client but we will come back to this after we get our rails app ready to authenticate against our Wordpress site.
Authenticating Rails Against Wordpress Oauth Provider
1. Create new rails app.
rails new omniauth-wordpress-oauth2-plugin-example . --database=sqlite3 -T
2. Add devise / omniauth gems to configuration file.
Easiest to just create the class app/controllers/omniauth_callbacks_controller.rb instead of running generator.
class OmniauthCallbacksController < ApplicationController
def wordpress_oauth2
#You need to implement the method below in your model (e.g. app/models/user.rb)
@user = User.find_for_wordpress_oauth2(request.env["omniauth.auth"], current_user)
if @user.persisted?
flash[:notice] = I18n.t "devise.omniauth_callbacks.success", :kind => "Wordpress Oauth2"
sign_in_and_redirect @user, :event => :authentication #this will throw if @user is not activated
else
session["devise.wordpress_oauth2_data"] = request.env["omniauth.auth"]
redirect_to new_user_registration_url
end
end
end
Update User model to find users by oauth provider data:
def self.find_for_wordpress_oauth2(oauth, signed_in_user=nil)
#if the user was already signed in / but they navigated through the authorization with wordpress
if signed_in_user
#update / synch any information you want from the authentication service.
if signed_in_user.email.nil? or signed_in_user.email.empty?
signed_in_user.update_attributes(email: oauth['info']['email'])
end
return signed_in_user
else
#find user by id and provider.
user = User.find_by_provider_and_uid(oauth['provider'], oauth['uid'])
#if user isn't in our database yet, create it!
if user.nil?
user = User.create!(email: oauth['info']['email'], uid: oauth['uid'], provider: oauth['provider'],
nickname: oauth['extra']['user_login'], website: oauth['info']['urls']['Website'],
display_name: oauth['extra']['display_name'])
end
user
end
end
Wrapping Up
Now when an authenticated resource is requested on your rails site, the user will be redirected to the wordpress auth provider to login. When the user has authenticated, they will be redirected back to your rails application and your app will receive a hash of user data passed from the authentication source:
Gits reflog is a powerful feature that allows a user to recover from almost any error. Github doesnt offer direct access to the reflog of the backing repository but using a couple of Githubs APIs, we can recover a commit from the remote reflog.
Agile and QA teams both have their compliment of Creatives who don’t fit the mold yet provide tremendous value to the team through the very traits that set them apart.