You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am successfully authenticating with e.g. router.get("/auth/", passport.authenticate("spotify", {})). But I'd like to send a custom param in the query string (e.g. the users timezone).
The docs say: In this example, note that authenticate() is called from within the route handler, rather than being used as route middleware. This gives the callback access to the req and res objects through closure
But that looks to be for writing my own strategy. I want to use the spotify strategy, but get access to that query string var from the original auth route.
This discussion was converted from issue #838 on July 13, 2021 00:14.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am successfully authenticating with e.g.
router.get("/auth/", passport.authenticate("spotify", {}))
. But I'd like to send a custom param in the query string (e.g. the users timezone).The docs say:
In this example, note that authenticate() is called from within the route handler, rather than being used as route middleware. This gives the callback access to the req and res objects through closure
But that looks to be for writing my own strategy. I want to use the spotify strategy, but get access to that query string var from the original auth route.
Is this possible?
Beta Was this translation helpful? Give feedback.
All reactions