[
https://issues.apache.org/jira/browse/KNOX-3276?focusedWorklogId=1009503&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1009503
]
ASF GitHub Bot logged work on KNOX-3276:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/26 08:33
Start Date: 13/Mar/26 08:33
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on PR #1176:
URL: https://github.com/apache/knox/pull/1176#issuecomment-4053572727
## Test Results
7 tests 7 ✅ 1s ⏱️
1 suites 0 💤
1 files 0 ❌
Results for commit 61982d14.
[test-results]:data:application/gzip;base64,H4sIAMLLs2kC/1WMyw6DIBQFf8Ww7gJoQejPNHiB5KYqDY9V038vWrW4OzMnmTfxOLpE7h27dCQVzAfYEk3GMG9Yj7xc/b4fqQCcxRNfVdBDeIPjSbgYQ9xMLPPeW2ab+/G/tnITW7ltQZgmzBWIZFpxy27g5dVwTaEfhLOMWtAatGKDEhK4FeTzBZgQh2D7AAAA
Issue Time Tracking
-------------------
Worklog Id: (was: 1009503)
Time Spent: 1h (was: 50m)
> 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
> 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)