Error Code: 1656
Getting the error message below when I try to use the default configuration of kinde, it will do it on register and login- user credentials go into the system on sign up but it will display the message below after logging in.
Something went wrong when we tried to authenticate you, and we can’t offer a quick way out. Start a new session and try signing in again. Error code: 1656
I am in a dev environment, I will supply env variables and kinde URLs when asked to do so for further support, thank you all for any help on this you can give.
5 Replies
Hi,
It looks like Error 1656 is related to issues with authentication and redirect URIs. possible causes include: 1. Missing nonce on implicit flow – Ensure that your authentication flow includes a valid nonce. 2. Redirect URI issue – Kinde requires a secure (
It looks like Error 1656 is related to issues with authentication and redirect URIs. possible causes include: 1. Missing nonce on implicit flow – Ensure that your authentication flow includes a valid nonce. 2. Redirect URI issue – Kinde requires a secure (
https://) redirect URI unless you are working on localhost. If your redirect URI starts with http:// (and it’s not a localhost domain), it will be rejected.
3. Malformed request – The request might be missing required parameters or include an invalid value.
4. Workflow error – There could be an issue with how the authentication workflow is set up.
To assist further, could you clarify the following?
- What is your current redirect URI configuration?
- Are you using http://localhost or another URL in your development environment?
- Are you using the implicit flow, and if so, is the nonce parameter included?
Providing these details will help us diagnose and resolve the issue more effectively1. In my env it is "KINDE_POST_LOGIN_REDIRECT_URL=http://localhost:3000/sign-up" and in Kinde i have this list for allowed callback URLs:
http://192.168.56.1:3000/api/auth/kinde_callback
http://localhost:3000/api/auth/kinde_callback
https://192.168.56.1:3000/sign-up
https://localhost:3000/sign-up
http://192.168.56.1:3000/sign-up
http://localhost:3000/sign-up
2. I am using http://localhost
3. I am not sure what nonce is (so I would assume I have not included this.. I cannot find this in the docs) and I'm not sure if im using implicit flow or not. I just did the quick start guide when I made my account, which is below.
- I made my .env.local file in root folder
- Made the respective path (src/app/api/auth/[kindeAuth]/route.js) and then put the following code below into it
import {handleAuth} from "@kinde-oss/kinde-auth-nextjs/server";
export const GET = handleAuth();
- In my page I added the respective <LoginLink> and <RegisterLink> componets
Hi, thanks for the additional details. Based on your configuration, I see that you're using http://localhost as your environment—which is acceptable for development—but your allowed callback URLs include both HTTP and HTTPS versions. One important point with Kinde is that, except for localhost, the redirect URI must be HTTPS.
It also appears that you’re not explicitly including a nonce parameter in your auth requests. In the implicit flow, the nonce is required to help mitigate replay attacks. Since you mentioned that you’re unsure if you’re using the implicit flow, here are a couple of clarifying questions:
- Are you using the implicit flow, or the authorization code flow? (The quick start guide you followed might be setting up the default flow, which could be the implicit flow.)
- Have you seen any configuration or documentation in your setup regarding nonce handling? The default quick start setup might not call it out explicitly.
- Can you confirm if your Kinde SDK version or configuration requires you to manually add a nonce parameter, or if it’s handled automatically?
Let me know if you have any questions or additional information
1. I am using Authorization Code Flow (not Implicit Flow), and the nonce is handled automatically by the SDK with my setup.
2. No I have not because I thought it was handled automatically through the SDK
3. I am not sure.
This has been resolved, it has gone away.
Hi Notall,
Glad to hear the issue has been resolved! If you run into any other problems or need further assistance, feel free to reach out. Happy coding
Glad to hear the issue has been resolved! If you run into any other problems or need further assistance, feel free to reach out. Happy coding