[
https://issues.apache.org/jira/browse/IGNITE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700776#comment-16700776
]
ASF GitHub Bot commented on IGNITE-9298:
----------------------------------------
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/5516
IGNITE-9298 SSL support in control.sh
I have merged two commits to get best of two worlds.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9298
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5516.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5516
----
commit 8de5e6fbb9e75deaff80337ae5e72675186653d8
Author: Ilya Kasnacheev <ilya.kasnacheev@...>
Date: 2018-11-27T17:39:19Z
IGNITE-9298 SSL support in control.sh
----
> control.sh does not support SSL
> (org.apache.ignite.internal.commandline.CommandHandler)
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-9298
> URL: https://issues.apache.org/jira/browse/IGNITE-9298
> Project: Ignite
> Issue Type: Bug
> Components: clients
> Affects Versions: 2.6
> Reporter: Paul Anderson
> Assignee: Paul Anderson
> Priority: Major
> Fix For: 2.8
>
> Attachments: Arguments.patch, CommandHandler.patch
>
>
> We required SSL on the connector port and to use control.sh to work with the
> baseline configuration.
> This morning I added support, see attached patches against 2.6.0 for
> org/apache/ignite/internal/commandline/CommandHandler.java
> org/apache/ignite/internal/commandline/Arguments.java
> No tests, no docs.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
