
kn2h0 (kn2h0) asked a question.
HI Team,
We have integrated an API Service into our application. However, when we attempt to generate a token using the Client Credentials method through the Swagger UI, an error arises. The error message indicates: "Authentication Error, error: invalid_client, description: Browser requests to the token endpoint must use Proof Key for Code Exchange."
We are seeking guidance on how to address this issue and successfully generate the token. It's worth noting that we lack a client app, and we are not employing the Proof Key for Code Exchange method for token generation. Is there a solution or configuration adjustment that can help us navigate this situation?

Hi @kn2h0 (kn2h0) , Thank you for reaching out to the Okta Community!
This question is more appropriate for our dedicated Okta Developer Forum.
My advice would be to reach out devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-developer work).
That being said, here are some older posts discussing a similar topic that might help you in the meantime:
https://support.okta.com/help/s/article/Browser-requests-to-the-token-endpoint-must-use-Proof-Key-for-Code-Exchange?language=en_US
https://devforum.okta.com/t/renew-access-token-browser-requests-to-the-token-endpoint-must-use-proof-key-for-code-exchange/21523/4
https://support.okta.com/help/s/question/0D54z00008SLTSLCA5/error-invalidclienterrordescription-browser-requests-to-the-token-endpoint-must-use-proof-key-for-code-exchange?language=en_US
https://devforum.okta.com/t/swagger-ui-browser-requests-to-the-token-endpoint-must-use-proof-key-for-code-exchange/15544
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
Okta Identity Engine (OIE) Ask Me Anything: Get answers from product experts by clicking here.