-
Notifications
You must be signed in to change notification settings - Fork 396
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
returnTo not working for me? #339
Comments
@adamjmcgrath I did try that too. Still the same on both localhost and deployed on my own domain. |
@tylernix - could you also share what version of Next.js, what version of Node and what version of this SDK you are using? |
Node v14.15.0
|
@tylernix Hmmm.. that looks fine. How are you triggering login? Via a link or the |
Ah, actually - I've spotted the issue export default handleAuth({
async loginHandler(req, res) {
export default handleAuth({
async login(req, res) { |
Ahhh! Beautiful! It worked. I copied and pasted that code from somewhere, but I just went back to handlers/login, and it does have the right code. 👍 Could this possibly have changed from the beta documentation to the latest 1.2.0 release? I have been working with this since the beta, so that is the only way I could explain things. Thanks again for your help! |
Cool, glad you got it working @tylernix
The behaviour hasn't changed - but there could be a bad example out there somewhere, if you spot it let me know |
I'll keep an eye out. But I haven't been able to find it in my last few minutes of searching, so maybe I am just crazy. I know at some point I had imported Thanks again for your help! I have enjoyed working with nextjs-auth0. |
Is there a specific format that the
returnTo
parameter is looking for in the LoginOptions being passed into the handleLogin function?It seems straightforward, but no matter what I do, it always redirects after a successful login to the AUTH0_BASE_URL.
My code:
The text was updated successfully, but these errors were encountered: