You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (Jira)" <ji...@apache.org> on 2020/11/19 13:36:00 UTC
[jira] [Updated] (IGNITE-13730) Unify fallback properties for SSL
settings as per Java standard
[ https://issues.apache.org/jira/browse/IGNITE-13730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Kasnacheev updated IGNITE-13730:
-------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> 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)