[
https://issues.apache.org/jira/browse/KNOX-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680693#comment-17680693
]
ASF subversion and git services commented on KNOX-2864:
-------------------------------------------------------
Commit fb685178890a5db337e7e69392ab4efc04ecf770 in knox's branch
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=fb6851788 ]
KNOX-2864 - TLS cipher suites and protocols are configured for CM service
discovery (#717)
In addition to the CM extension, we now have the ability to indicate TLS
protocols we'd like to include (not only the ones to exclude).
> Make TLS protocol and cipher suites configurable with CM service discovery
> --------------------------------------------------------------------------
>
> Key: KNOX-2864
> URL: https://issues.apache.org/jira/browse/KNOX-2864
> Project: Apache Knox
> Issue Type: Improvement
> Components: cm-discovery, Server
> Affects Versions: 2.0.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 2.1.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The goal of this Jira is to guarantee:
> * Knox picks up defaults in Java's {{java.security}} file in terms of
> disabled algorithms as well as TLS protocols and cipher suites
> * Also, we want these attributes to be configurable in the
> [DiscoveryApiClient|https://github.com/apache/knox/blob/master/gateway-discovery-cm/src/main/java/org/apache/knox/gateway/topology/discovery/cm/DiscoveryApiClient.java]
> class using the already existing gateway-level config.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
