[
https://issues.apache.org/jira/browse/KNOX-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-3276:
--------------------------------
Description:
As of today, Knox uses its own server-side TLS configuration in
DiscoveryApiClient when it comes to configuring SSL between Knox and CM.
However, this might not overlap and CM uses a separate set of TLS
ciphers/protocols. To address that, we will need to add new configs to control
the SSL settings within the CM API client.
was:
As of today, Knox uses its own server-side TLS configuration in
DiscoveryApiClient when it comes to configuring SSL between Knox and CM.
However, this might not overlap and CM uses a separate set of TLS
chiphers/protocols. To address that, we will need to add new configs to control
the SSL settings within the CM API client.
> Add new config that controls TLS settings in CM client
> ------------------------------------------------------
>
> Key: KNOX-3276
> URL: https://issues.apache.org/jira/browse/KNOX-3276
> Project: Apache Knox
> Issue Type: Task
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 3.0.0
>
>
> As of today, Knox uses its own server-side TLS configuration in
> DiscoveryApiClient when it comes to configuring SSL between Knox and CM.
> However, this might not overlap and CM uses a separate set of TLS
> ciphers/protocols. To address that, we will need to add new configs to
> control the SSL settings within the CM API client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
