-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: apisix 2.15.1 do not accept private CA (worked in apisix 2.13.0) #8568
Comments
|
Hi @tokers
At the times of apisix 2.12.0 the tls settings of the helm chart were sufficient (see #6345 ) What can I do? |
I don't thinks this can be done unless you update the base image (adding your private CA to the system trusted CA bundles)
Could you please paste the |
Well the lua_ssl_trusted_certificate is
But I don't know how to set values in the helm chart to change this configuration The complete nginx.conf is
|
@MirtoBusico Hi, have you ever checked the contents in |
Hi @tokers
On the Apisix pod the /usr/local/apisix/conf/ssl/cert is
(Seems equal) Issuing wget with --ca-certificate from Apisix pod says
Issuing wget without --ca-certificate from Apisix pod says
Can I look at someting else? |
That's a normal situation. I want to know after you configure the CA cert to APISIX, is it normal for APISIX to communicate with your keycloak server? From the error logs you pasted:
There is no direct evidence shows it's caused by an unknown CA. |
Well @tokers when I tried to use openid-connect (see #8452 ) the cause was identified in #8068 But when I discovered that a wget in the apisix pod was not able to communicate with the keyclok server I supposed that there was another problem, so I reported here Do you think that there is no relation between the failing wget and the apisix pod accessing the keycloak server? BTW when in the past I encountered this issue (see #6345 ) in the apisix pod I used curl and I was able to reach the keycloak server (apisix image was tagged 2.13.0-alpine ). Now curl is not installed and I had to use wget (apisix image is tagged 2.15.1-debian ) |
From the error log's point of view, I think it's not related to the CA. Not sure how you invoke the curl command. 😁 |
Ok @tokers I think you can close the issue |
Did you solve the issue? :) |
Well, no |
Got it. Let's troubleshoot it in another issue. |
Current Behavior
I have a keycloak server with certificates signed by a private Certification Authority.
Apisix is installed via helm chart in kebernetes
The apisix pod is not able to access the keycloak server saying that the issuer is unknown
I created a kubernetes secret:
and referenced the secret in the tls section of the gateway (in helm chart values.yaml)
What can I do?
Expected Behavior
In apisix 2.13.0 it worked correctly
I created the secret:
Instered the secret in the tls section of gateway (in values.yaml file of the helm chart)
Error Logs
Tryin to access the keycloak server gives the issuer unknown error
Steps to Reproduce
Environment
apisix version
):uname -a
):openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):The text was updated successfully, but these errors were encountered: