#304 OmniAuth Identity

Ryan,

Great screencast!

One thing though.. you did not illustrate how to remove the default OmniAuth identity pages once you've created your own.

-ra

i think rails should have an authentication and permission engine by default. Anyway sorcery authentication looks much more clean to me.

Thanks for doing this Ryan. Again, you have read my mind by creating this. Also, thanks to Intridea for kicking ass!

You can also pass other options such as form in the initializer to override the login form. Like this:

provider :identity,
    form: lambda { |env| SessionsController.action(:new).call(env) },
    on_failed_registration: lambda { |env| UsersController.action(:new).call(env) }

Added a link to the 'cast to the project README. Thanks, Ryan!

If working with an app to provide email/password AND external authentication, would this be the way to go over OmniAuth/Devise in combination?

Great screencast Ryan, shows how great tool omniauth is. I just have one question, kinda in the lines of what Josh said earlier - how do you integrate this with Devise? I noticed there are no features like forgot password or confirmation emails using identity so how would you go about implementing those?

Excellent screencast Ryan! Always incredibly helpful!

By the way, I created a basic formatting gem based on your gem publishing screencast called validates_formatting_of. This eliminates the need for pasting in special regex (and allows custom regex if you want). Thought I would throw that out there for you to take a look at.

I was getting 401: Unauthorized errors for twitter so decided to give Facebook a try. This caused

{ "error": { "message": "Missing client_id parameter.", "type": "OAuthException" } }

The solution was to remove the ENV[ ] from the initialiser for both twitter and facebook and it seems to be working fine.

I personally prefer how you integrated omniauth with Devise in episode #236. Do we need to point the omniauth gem to an earlier version to keep that working?

Hi,

I downloaded the source code, when I try to use google (and I need to use it), I get

http://localhost:3000/auth/failure?message=invalid_credentials

Any hint please?

I'm using this, and wondering how you can tell the difference between a new registration and a login, since they both hit the same callback URL. I'd like to collect some metrics on sign-ups, but I'm not sure how I would be able to tell in the rails app.

Another outstanding video - thank you! A question (perhaps a novice question):

how can I enable users to register so that all of the services record their "first_name" in the user model rather than "name" which is required in the auth hash schema?

It seems that omniauth-identity requires "name" while with omniauth-facebook I can distinguish between "name" and "first_name" and "last_name" when the user model creates records.

I do not work the path "/auth/google_apps" on the form, change it to "/auth/google_oauth2" and works great!!

Hi,
i'm trying to extend this example with json response
in session controller

def create
auth = request.env["omniauth.auth"]
user = User.where(:provider => auth['provider'],
:uid => auth['uid']).first || User.create_with_omniauth(auth)
session[:user_id] = user.id
respond_to do |format|
format.html { redirect_to root_url, :notice => 'Signed in!'}
format.json { render :json => user }
end
end

Started POST "/auth/identity/callback.json"
i got error 500

NoMethodError (You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.[]):
app/controllers/sessions_controller.rb:10:in `create'

coresponding with this code in the session create controller

user = User.where(:provider => auth['provider'], 
                  :uid => auth['uid']).first || User.create_with_omniauth(auth)

How to add json response in this schema?
i need able authorize to my site via mobile app

Can I ask a couple of questions here Ryan or others.

1) does the "sign in with google" use OAuth-2 or OpenID? Getting confused here. Reading the google pages it almost seems you need to use OpenID for "sign in using google", and OAuth to get data via google api's?

2) if I want to both (a) use "sign in with google" for authentication, and also (b) access data from a google api, then do I need to use two separate processes in rails for this? E.g. do I need to use say (a) OmniAuth to do the "sign in with google", and then (b) OAuth Plugin configured to google calendar API to get the data?

I ask this last question noting I've successfully so far used (a) OmniAuth to do the "sign in with google", and (b) OAuth Plugin to get google calendar API data.

I'm running into a strange problem with cucumber. When I run my feature that tests that a user can create an account, the feature fails with the error No route matches [POST] "/auth/identity/register" (ActionController::RoutingError) It does, however, work just fine if I test it in my browser. Running rake routes dos not show that route, but I assume that's because it's provided by omniauth-identity through rack middleware. Does anyone have any ideas? Any Google searches I've done just bring me back here. Thanks for the great screencast!

Just an fyi, using Rack 1.4.0 may cause the following error, undefined method 'include?' for nil:NilClass. Upgrading to 1.4.1 fixed the problem.

ref: Link

Does anyone know how to make the custom login form remember login details? E.g. when I type my email but with an incorrect password it now forgets about the email address.

What about we don't get user email from twitter, and I want user to specify it manually like you did with devise+omniauth in ep 236?

Help!, I'm tring to create an omniauth-identity login following the screencast but I get the following error;

ActiveModel::MassAssignmentSecurity::Error

Can't mass-assign protected attributes: password, password_confirmation

I'm a little bit confused. Previously you made all Omniauth authentication options exist via the authentication model. Here you seem to have broken from that by making the user the authentication provider holder. Why isn't identity just another authentication?

The challenge I see is that I want to manage roles for a user, but with the user constructed the way that it is, it would appear I have to create another variation of a user model in order to do make a user a truly singular entity (with many users instead of authentications? both users and authentications?)

Hi,

I did all like in the guide, but on failed registration I got the following:

Routing Error

No route matches {}
Try running rake routes for more information on available routes.

Details of my issue can be found at http://stackoverflow.com/questions/11506734/routing-error-no-route-matches-when-omniauth-failed-on-registration

Does anybody have any ideas what can be the reason for this?

I've played a lot with OmniAuth Identity, and in the end for the little it provides, I don't think it's worthwhile.

I found that after having to override it's views, and having to add password recovery, authentication redirection and session remember me functionality myself, I may as well just use Rails 3's has_secure_password myself. I've ditched OmniAuth Identity in favor of Rails built-in has_secure_password, and I'm much happier and find it's much cleaner and nothing is abstracted away.

You might have trouble authenticating with Google, under sessions/new.html.erb on line 30 replace:

a href="/auth/google_apps" class="auth_provider"

with

a href="/auth/google_oauth2" class="auth_provider"

I set this up exactly as the RailsCast suggested. When I'm creating an identity it populates the identity table with the login information, however, it doesn't connect this data to the user table until the user actually logs in.

According to the logs it looks for a null email then throws an error "/auth/failure?message=invalid_credentials".

I'm probably missing something very simple. The only change I made was replacing first_name and last_name with name.

Started POST "/auth/identity/register" for 127.0.0.1 at 2012-12-13 08:28:44 -0500
(57.1ms) BEGIN
Identity Exists (55.7ms) SELECT 1 AS one FROM identities WHERE identities.email = BINARY 'email@email.com' LIMIT 1
SQL (56.5ms) INSERT INTO identities (created_at, email, first_name, last_name, password_digest, sha_password, updated_at) VALUES ('2012-12-13 13:28:44', 'email@email.com', 'first', 'last', '$2a$10$o4axANSpONo.GsIRIqpWET5FG', NULL, '2012-12-13 13:28:44')
(56.8ms) COMMIT
Identity Load (55.4ms) SELECT identities.* FROM identities WHERE identities.email IS NULL LIMIT 1

Started GET "/auth/failure?message=invalid_credentials" for 127.0.0.1 at 2012-12-13 08:28:44 -0500
Processing by SessionsController#failure as HTML
Parameters: {"message"=>"invalid_credentials"}
Redirected to http://localhost:3000/
Completed 302 Found in 1ms (ActiveRecord: 0.0ms)

Started GET "/assets/rails.png" for 127.0.0.1 at 2012-12-13 08:28:44 -0500
Served asset /rails.png - 304 Not Modified (0ms)
[2012-12-13 08:28:44] WARN Could not determine content-length of response body. Set content-length of the response or set Response#chunked = true

Hi!
I want to add "sign in with google" to my application. I already have Twitter and Facebook based on episode 235 "Devise and omniauth" and their implementations were fair and simple.

Is it the omniauth-google_oauth2 gem I should use if I want people to be able to login with their gmail-accounts? If so, where will I find the ['GOOGLE_KEY'] and ['GOOGLE_SECRET']?. Is it by visiting https://code.google.com/apis/console/ and creating an api and using "Client ID" and "Client secret" from there? Or do I have to create some google business app or something?

I mean with Twitter and Facebook I only had to go to their dev-pages and create an app and then it was ready to use.

Or is it an entirely other omniauth gem I should use if I want people to login with gmail/google-accounts?

regards!

Hi. Im using Rails 4 and getting errors. I have followed episode 241 and the twitter integration works perfect. In this episode Im getting:

No route matches [POST] "/auth/identity/callback"

Is it because Im using Rails 4?

Yes, there are some changes with how routes are defined in Rails 4.

Go into config/routes.rb and change your /auth/:provider/callback route to accept :post requests:

# Rails 4 route syntax
match '/auth/:provider/callback', to: 'sessions#create', via: [:get, :post]
# or, explicitly accept post requests
post '/auth/:provider/callback' => 'sessions#create'

Thank you Dave that sorted out my ongoing problem