Invalid_client error on Service ID despite successful manual token exchange test

Hi

I am experiencing a persistent 'invalid_client' error when attempting to exchange the authorization code for an access token using Sign in with Apple for my website (https://www.vitamarinaweb.com).

Current Setup & Steps Taken:

Identifier: I am using the Service ID com.vitamarinaweb.web1, which is correctly linked to the Primary App ID com.vitamarinaweb.web.

Client Secret: I have generated a fresh Client Secret (JWT) using a valid Key (.p8) and confirmed the Team ID (29J763Q88J) and Key ID (RRW6536D27) are correct.

Redirect URIs: My Return URL is set to https://www.vitamarinaweb.com/login.php and I have verified there are no trailing spaces or mismatches.

Manual Test (CURL): When I perform a manual POST request via CURL using the generated Client Secret, I receive an 'invalid_grant' response (meaning the Client Secret and Client ID are accepted, and only the temporary code is rejected as expected).

The Issue: Despite the CURL success, every request initiated through the web browser/PHP application returns {"error":"invalid_client"}.

Verification Requested:

Could you please verify if there is a synchronization delay or a specific block on Service ID com.vitamarinaweb.web1?

Is there any internal mismatch between the Key ID RRW6536D27 and its association with the newly created Service ID?

I have already cleared browser caches and tried multiple devices (different IP addresses) with the same result.

Thank you for your assistance."

Answered by jim88 in 872990022

Ok , I'm solved the issue it was the segret key format, thank you

Accepted Answer

Ok , I'm solved the issue it was the segret key format, thank you

Invalid_client error on Service ID despite successful manual token exchange test
 
 
Q