You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ssl object definition in the apisix/schema_def.lua file mentions that it allows for input in the form of sni, cert, key, snis, certs, keys, i.e. it allows for multiple SNIs to be configured for a single SSL object, and support multiple certificate pairs.
There is some misunderstanding here, the docs say that the first certificate should be configured using cert and subsequent ones using certs. nevertheless, this is really rather unintuitive and counter-intuitive.....
Current Behavior
The
ssl
object definition in theapisix/schema_def.lua
file mentions that it allows for input in the form ofsni
,cert
,key
,snis
,certs
,keys
, i.e. it allows for multiple SNIs to be configured for a single SSL object, and support multiple certificate pairs.In the following logic flow it is written:
This means that I can't pass schema check with
certs
andkeys
configured anyway. So what is the point of certs and keys?I think this is a significant bug. And it's been around for 20 months [#7221].
Further, even if I manually change it to
certs
andkeys
, it doesn't configure properly and more bugs are happening.Even if there are no bugs sent, there is a logical error in schema, why snis, certs, keys must exist at the same time? it is absurd.
A possible option is to allow oneOf:
By the way, I don't think this has anything to do with the GM plugin, which implements [#8389] after the bug.
Expected Behavior
Allows multiple certificates to be properly configured on a single SSL object via the APISIX Admin API.
Error Logs
No response
Steps to Reproduce
Environment
apisix version
): 3.8.0uname -a
): not relatedopenresty -V
ornginx -V
): not relatedcurl http://127.0.0.1:9090/v1/server_info
): not relatedluarocks --version
): not relatedThe text was updated successfully, but these errors were encountered: