If you encounter issues while integrating Kenni, it's often due to a misconfiguration. The Kenni error page typically offers clues about the problem, though some cases can be trickier to diagnose. We'll continue to expand this section with more helpful content over time.
When getting tokens: invalid_client, client authentication failed
This error can occur after a user has completed authentication in Kenni and been redirected to your application's redirect URL. At this point, your application attempts to call Kenni's token endpoint to exchange the authorization code for user tokens (such as ID token, access token, and refresh token).
The issue may also arise with machine-to-machine clients when requesting tokens from the token endpoint.
This error indicates a problem with client authentication in the request.
- Ensure you've configured the correct Client ID and Client Secret in your application.
- For "Web (SPA)" or "Native" client types, send only the Client ID—not the Client Secret.
- For "Web" or "Machine to Machine" client types, send both the Client ID and Client Secret.