[
https://issues.apache.org/jira/browse/KNOX-3276?focusedWorklogId=1009526&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1009526
]
ASF GitHub Bot logged work on KNOX-3276:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/26 11:15
Start Date: 13/Mar/26 11:15
Worklog Time Spent: 10m
Work Description: smolnar82 merged PR #1176:
URL: https://github.com/apache/knox/pull/1176
Issue Time Tracking
-------------------
Worklog Id: (was: 1009526)
Time Spent: 1h 10m (was: 1h)
> 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
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
