Routing error with OmniAuth

Hello,

I am trying to use OmniAuth with Devise and I am stumbling on some
initial step. When I go to localhost:3000/auth/twitter I get a routing
error

No route matches "/auth/twitter"

I have the "gem omniauth" in my gemfile and I have omniauth.rb where I
have setup twitter connection as below

Rails.application.config.middleware.use OmniAuth::Builder do
  provider :twitter, 'MY KEY', 'MY SECRET'
end

The server starts up fine - the home page loads. I am on Ruby
1.9.2p180 and Rails 3.0.5 on a Win box.

Thanks for any pointers on what I may be missing here.
-S

Phil

Hello,

I am trying to use OmniAuth with Devise and I am stumbling on some

initial step. When I go to localhost:3000/auth/twitter I get a routing

error

No route matches “/auth/twitter”

I have the “gem omniauth” in my gemfile and I have omniauth.rb where I

have setup twitter connection as below

Rails.application.config.middleware.use OmniAuth::Builder do

provider :twitter, ‘MY KEY’, ‘MY SECRET’

end

The server starts up fine - the home page loads. I am on Ruby

1.9.2p180 and Rails 3.0.5 on a Win box.

Thanks for any pointers on what I may be missing here.

Given the error, you’re probably missing a route. The gem does not provide automatically provide one (at least, it didn’t when I used it), you’ll need to add it to the routes file.

Phil

> Hello,

> I am trying to use OmniAuth with Devise and I am stumbling on some
> initial step. When I go to localhost:3000/auth/twitter I get a routing
> error

> No route matches "/auth/twitter"

> I have the "gem omniauth" in my gemfile and I have omniauth.rb where I
> have setup twitter connection as below

> Rails.application.config.middleware.use OmniAuth::Builder do
> provider :twitter, 'MY KEY', 'MY SECRET'
> end

> The server starts up fine - the home page loads. I am on Ruby
> 1.9.2p180 and Rails 3.0.5 on a Win box.

> Thanks for any pointers on what I may be missing here.

Given the error, you're probably missing a route. The gem does not provide
automatically provide one (at least, it didn't when I used it), you'll need
to add it to the routes file.

That would be the natural conclusion - missing something in routes.rb
- but I checked Ryan Bates' screencast (downloaded his screencast code
and looked in the routes.rb file there) and other Omniauth
documentation and unless I am missing something staring in my face, I
don't see anything added to routes.rb for this. Per the documentation
you do need to add to routes.rb to handle the callback (/auth/twitter/
callback) but nothing for the initial call to /auth/twitter.

Thanks for thoughts or pointers you can help provide.