Empty response when requesting for token with 200 status
Hi team, I'm trying to integrate kinde with my angular SPA, I'm using the community angular sdk
the login request with the is sent correctly and the login from kinde returns 200 but with an empty body
I'm using social login with google, my app will be passwordless,
what could be the reason for an empty body on token request?
6 Replies
Hi dariogriffo,
Thanks for reaching out.
It looks like your Angular SPA is successfully receiving a
200 status from Kinde during the login process, but the response body is empty when using Google social login.
To help diagnose the issue, could you please confirm the following:
1. Are you using the latest version of the Kinde Angular SDK?
2. Have you configured your Google social login correctly in the Kinde dashboard?
3. Are you seeing any errors or warnings in the browser console during the login process?
4. Could you share your current configuration or code snippet related to the login process?
These details will help us identify the cause and provide the right solution.1- yes, version 1.4.1
2- I think so, I can login, the problem is with the token endoint
3- no errors, no warnings
4- attached screenshot for login and token
the payload sent by angular seems ok,
I see the token set in the cookies, but is not handled by angular, not stored in the session
still cant get the token endpoint to return a valid token, so far the token is stored as a cookie when google redirects to my website again, the token is issued by kinde, but I would like to know what can I do to manage the lifetime of the token and get a token myself
Hi dariogriffo,
Thanks for confirming. Here are some steps you can try to resolve the issue:
1. Check the POST Payload:
- Refer to Kinde’s guide: Using Kinde without an SDK.
- Ensure the POST request to
https://<your-subdomain>.kinde.com/oauth2/token includes all required fields (e.g., grant_type, client_id, client_secret, redirect_uri, code, code_verifier).
- Compare your request with the cURL example: Access Token for API.
2. Token Retrieval with SDK:
- Use await kinde.getToken() after the SDK initializes.
- Move the getToken() call to ngOnInit() or after the handleRedirectCallback() promise resolves.
- See Kinde’s docs: JavaScript SDK.
3. PKCE Code Verifier Mismatch:
- An empty JSON response might indicate a mismatch between the code verifier sent during authorization and the one used for the token exchange.
- Log both values in localStorage/sessionStorage to verify they match.
4. SDK Version Issues:
- Update to the latest @kinde/auth-angular version.
- Check the changelog for fixes related to PKCE or cookie handling: Kinde Auth React Issue.
5. API Configuration:
- Verify scope and audience settings in the Kinde Dashboard under Settings → Applications.
- Make sure your M2M app has the correct scopes and audience: Troubleshoot Kinde API.
Try these steps one by one, and you’ll likely find the root cause. Feel free to reach out if you encounter any issues or have additional questions.GitHub
Issues · kinde-oss/kinde-auth-react
Kinde React SDK for frontend authentication flows. Contribute to kinde-oss/kinde-auth-react development by creating an account on GitHub.
Hi dariogriffo,
Just following up to see if you’ve had a chance to try the troubleshooting steps we shared regarding the empty token response with your Angular app.
Please let us know if the issue persists or if you need any further assistance; otherwise, we will go ahead and close this. Feel free to reach out anytime