RailsCasts Pro episodes are now free!

Learn more or hide this

Richard Rosa's Profile

GitHub User: richrosa

Comments by Richard Rosa


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 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 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 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