search

wso2 / product-microgateway

Choreo Connect is a cloud-native, open-source, and developer-centric API gateway.
https://wso2.com/choreo/choreo-connect/
Apache License 2.0
287 stars 246 forks source link

[Choreo Connect 1.0.0] Cannot configure TLS and cipher versions for the downstream #3467

Closed Sumudu-Sahan closed 7 months ago

Sumudu-Sahan commented 7 months ago

Description

Cannot configure TLS and cipher versions for the downstream which is similar to the upstream of the CC [1]

[1] https://apim.docs.wso2.com/en/latest/deploy-and-publish/deploy-on-gateway/choreo-connect/configurations/router-configurations/#upstream-tls

Steps to Reproduce

When running the testsslserver.jar file by pointing to the CC, able to see the observations even after adding the [router.upstream.tls] configurations because this is not reflected in the downstream.

sumudu@sumudu:~/Downloads/testsslserver-jar$ java -jar TestSSLServer.jar apim 9095
Supported versions: TLSv1.0 TLSv1.1 TLSv1.2
Deflate compression: no
Supported cipher suites (ORDER IS NOT SIGNIFICANT):
  TLSv1.0
     RSA_WITH_AES_128_CBC_SHA
     RSA_WITH_AES_256_CBC_SHA
  (TLSv1.1: idem)
  TLSv1.2
     RSA_WITH_AES_128_CBC_SHA
     RSA_WITH_AES_256_CBC_SHA
     TLS_RSA_WITH_AES_128_GCM_SHA256
     TLS_RSA_WITH_AES_256_GCM_SHA384
----------------------
Server certificate(s):
  16fc95e22ccb0c4924f3003d5f3306521243d153: CN=localhost, OU=WSO2, O=WSO2, L=Mountain View, ST=CA, C=US
----------------------
Minimal encryption strength:     strong encryption (96-bit or more)
Achievable encryption strength:  strong encryption (96-bit or more)
BEAST status: vulnerable
CRIME status: protected

Version

1.0.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response