[
https://issues.apache.org/jira/browse/IGNITE-13730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235466#comment-17235466
]
Ignite TC Bot commented on IGNITE-13730:
----------------------------------------
{panel:title=Branch: [pull/8477/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8477/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5742235&buildTypeId=IgniteTests24Java8_RunAll]
> Unify fallback properties for SSL settings as per Java standard
> ---------------------------------------------------------------
>
> Key: IGNITE-13730
> URL: https://issues.apache.org/jira/browse/IGNITE-13730
> Project: Ignite
> Issue Type: Improvement
> Components: networking
> Reporter: Ilya Kasnacheev
> Assignee: Ilya Kasnacheev
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now we use e.g. "ssl.key.algorithm" which is not standard. Standard
> option for this setting appear to be "javax.net.ssl.trustStoreProvider" and
> "javax.net.ssl.keyStoreProvider" as per
> https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.base.doc/ae/tjj_thirdparty_ssl.html
> We should make sure that "javax.net.ssl.keyStoreProvider" is the default
> fallback property for any SSL-using code: discovery, communication, thin
> clients, etc. Our own properties should be kept for compatibility reasons.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
