[GitHub] [apisix] zhukexingkong removed a comment on issue #6429: request help: A TLS API is routed, but the Client Key is different from the original one

[GitBox <gi...@apache.org>]

zhukexingkong removed a comment on issue #6429:
URL: https://github.com/apache/apisix/issues/6429#issuecomment-1057621767


   > I reproduced. You should delete the first paragraph of the client.key. like this：
   > 
   > ```
   > Bag Attributes
   >     friendlyName: client
   >     localKeyID: 54 69 6D 65 20 31 36 34 36 31 31 38 36 33 35 38 32 31
   > Key Attributes: <No Attributes>
   > ```
   > 
   > And then, upload the file.
   
   Error reporting is back to square one.
   When I modified the client.key, the following error occurred. If config.yaml needs to be modified if upstream enables TLS, I will do so, but the official document does not seem to indicate that needs to modify config.yaml for upstream TLS.
   Note: the system is centos7
   
   [root@2d8f65f7ad67 tlsDir]# python ./patch_upstream_mtls.py 396921614249231056 ./client.pem ./client.key
   404
   {"message":"Key not found"}
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org