Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

passport-twitter + restify --> "message": "OAuth authentication requires session support" #90

Closed
arcmode opened this issue Jan 7, 2013 · 7 comments

Comments

@arcmode
Copy link

arcmode commented Jan 7, 2013

I have passport-facebook working but with passport-twitter I get the following error:

{
"message": "OAuth authentication requires session support"
}

Does anyone have a working example using passport-twitter and restify.

BTW, my app is targeted as an API so I would prefer not to use sessions at all.

Thanks,

David

@marcusbaguley
Copy link

You have no doubt solved it now, but I had this problem and it turned out my app.get('/auth/twitter', passport.authenticate('twitter')) route was inside the exports.init function....

@pavelnikolov
Copy link

I have the same problem. I was able to make passport-facebook to work properly with my restify API, but passport-twitter returns "{"message":"OAuth authentication requires session support"}"

@pavelnikolov
Copy link

It turned out that that similar code works with facebook because passport-facebook uses OAuth 2.0 and passport-twitter uses OAuth 1 which requires session. So the problem is that we are not using session in our APIs.

@skeeet
Copy link

skeeet commented Jun 6, 2013

So how do you solved that finally?
AFAIK Restify have no sessions support. Did you set up separate server or did your own sessions implementation?

@pavelnikolov
Copy link

I decided not to use twitter login for the moment

@hueitan
Copy link

hueitan commented Sep 3, 2014

Still having the problem on Sep 2014

@jaredhanson
Copy link
Owner

OAuth 1 requires sessions, which is what the error is stating. It is not possible to make it work securely without sessions, so closing this issue as won't fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants