-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
Error: Failed to find request token in session #101
Comments
What is your |
@Martii What do you mean by |
We use this auth strategy with the |
Btw...
Is your localhost https? Most aren't and use http with no certificates... but depends on your network setup. |
I am using ngrok. I haven't had this issue 3 days ago. |
Unfamiliar with that particular tunneling reverse proxy... perhaps they updated something in their backend or your frontend? Have you tried direct to your development environment on the same LAN? You are welcome to give OUJS as shot to see if you can sign up/sign in with your twitter account... we haven't gotten any issues yet and the code point reference above I gave you is how we handle all the strategies with the |
I've tried setting the cookie to LAX, strict and the other options and still no luck. I am going to check to see if I have the same issue with passport Twitter libraries. |
Oh forgot I am testing this in Firefox. |
I am getting this error when trying to do this with next.js
|
Hope you are returning profile in cb:
And nothing else |
Yeah, this is partly an issue with next.js. in Dev mode it throws the session away most of the time. No idea why. |
Error: Failed to find request token in session at SessionStore.get (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\passport-oauth1\lib\requesttoken\session.js:13:44) at Strategy.OAuthStrategy.authenticate (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\passport-oauth1\lib\strategy.js:214:33) at Strategy.authenticate (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\passport-twitter\lib\strategy.js:87:40) at attempt (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\passport\lib\middleware\authenticate.js:361:16) at authenticate (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\passport\lib\middleware\authenticate.js:362:7) at Layer.handle [as handle_request] (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\layer.js:95:5) at next (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\route.js:137:13) at Route.dispatch (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\route.js:112:3) at Layer.handle [as handle_request] (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\layer.js:95:5) at C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:281:22 at Function.process_params (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:335:12) at next (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:275:10) at Function.handle (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:174:3) at router (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:47:12) at Layer.handle [as handle_request] (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\layer.js:95:5) at trim_prefix (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:317:13) at C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:284:7 at Function.process_params (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:335:12) at next (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:275:10) at initialize (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\passport\lib\middleware\initialize.js:53:5) at Layer.handle [as handle_request] (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\layer.js:95:5) at trim_prefix (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:317:13) at C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:284:7 at Function.process_params (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:335:12) at next (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express\lib\router\index.js:275:10) at C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\express-session\index.js:489:7 at Command.callback (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\connect-redis\lib\connect-redis.js:167:14) at normal_reply (C:\Users\danie\WebstormProjects\socialrewards\socialrewards\node_modules\redis\index.js:726:21)
How to reproduce
What am I using.
express-session
app.use(session({ store: new RedisStore(redis_options), secret: process.env.EXPRESS_SESSION_SECRET, resave: true, saveUninitialized: true, cookie: { secure: true } }));
In a development environment
Things I have already tried
Changing
app.use(session({ store: new RedisStore(redis_options), secret: process.env.EXPRESS_SESSION_SECRET, resave: true, saveUninitialized: true, cookie: { secure: true } }));
to
app.use(session({ store: new RedisStore(redis_options), secret: process.env.EXPRESS_SESSION_SECRET, resave: true, saveUninitialized: true, cookie: { secure: 'auto' } }));
and then to
app.use(session({ store: new RedisStore(redis_options), secret: process.env.EXPRESS_SESSION_SECRET, resave: true, saveUninitialized: true }));
I regenerated both Auth tokens and API information in my twitter app.
Ran the app on https and http
Has anyone solved this problem before?
The text was updated successfully, but these errors were encountered: