Kinde Webhook
Dear Kinde Support Team,
We are encountering a persistent issue with webhook requests sent to our endpoint "https://{*******}.convex.site/kinde-webhook". Our logs indicate that the
Additionally, we've faced repeated issues with JSON parsing errors, specifically an "Unexpected token 'e'" error, suggesting that the payload might be incorrectly formatted or encoded. Here is an example of the error message from our logs:
- Error parsing JSON: [SyntaxError: Unexpected token 'e', "eyJhbGciOi"... is not valid JSON]
Here are the headers received with one such problematic request:
- Host: {**}.convex.site
- User-Agent: Go-http-client/2.0
- Content-Length: 774
- Accept-Encoding: gzip
- Content-Type: application/json
- Webhook-ID: 80a74830**
- Webhook-Timestamp: 1715521568
- X-Forwarded-For: *
- X-Forwarded-Host:{}.convex.site
- X-Forwarded-Proto: http
- Convex-Request-ID: **
Despite multiple attempts to rectify this issue by checking our configuration and validating incoming data formats, the problem persists. We expected the JWT to be included in the
Could you please investigate on your end why the
Thank you for your attention to this matter.
We are encountering a persistent issue with webhook requests sent to our endpoint "https://{*******}.convex.site/kinde-webhook". Our logs indicate that the
AuthorizationAdditionally, we've faced repeated issues with JSON parsing errors, specifically an "Unexpected token 'e'" error, suggesting that the payload might be incorrectly formatted or encoded. Here is an example of the error message from our logs:
- Error parsing JSON: [SyntaxError: Unexpected token 'e', "eyJhbGciOi"... is not valid JSON]
Here are the headers received with one such problematic request:
- Host: {**}.convex.site
- User-Agent: Go-http-client/2.0
- Content-Length: 774
- Accept-Encoding: gzip
- Content-Type: application/json
- Webhook-ID: 80a74830**
- Webhook-Timestamp: 1715521568
- X-Forwarded-For: *
- X-Forwarded-Host:{}.convex.site
- X-Forwarded-Proto: http
- Convex-Request-ID: **
Despite multiple attempts to rectify this issue by checking our configuration and validating incoming data formats, the problem persists. We expected the JWT to be included in the
AuthorizationBearer <token>Could you please investigate on your end why the
AuthorizationThank you for your attention to this matter.
