Help Center/ API Gateway/ FAQs/ API Policies/ Why Am I Seeing "Public key does not exist" When an API Bound to a JWT Authentication Policy Is Called?

Updated on 2025-10-31 GMT+08:00

View PDF

Why Am I Seeing "Public key does not exist" When an API Bound to a JWT Authentication Policy Is Called?

If the public key of the JWT authentication policy is obtained in scheduled mode, check whether the entered JWKS_URI remote service is running properly and whether the JWKS public key response is returned. In addition, check whether the returned public key complies with the correct JWKS format.
Ensure the kid in the request token matches one of the public keys in the JWKS. The gateway uses kid to locate the key; if no match is found, the error will occur.

Parent topic: API Policies

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.