[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640441#comment-17640441
]
Janos Makai commented on OOZIE-3674:
------------------------------------
I've narrowed down the testing of insecure connection in
`TestInsecureConnection` to prevent the IO exceptions during runs, hence
preventing the timeouts.
[~dionusos] could you please have a check on the latest patch set?
The SpotBugs bugs are not related to this change.
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> -----------------------------------------------------------------------------------
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
> Affects Versions: 5.2.1
> Reporter: Janos Makai
> Assignee: Janos Makai
> Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch,
> OOZIE-3674-003.patch, OOZIE-3674-004.patch, OOZIE-3674-005.patch,
> OOZIE-3674-006.patch, OOZIE-3674-007.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
