[
https://issues.apache.org/jira/browse/OOZIE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Janos Makai updated OOZIE-3677:
-------------------------------
Description:
In scope of making Oozie FIPS compliant, when TLS is enabled, the Oozie server
expects a JKS KeyStore type even though the following Java system properties
are being set:
{code:java}
-Djavax.net.ssl.keyStoreType=bcfks -Djavax.net.ssl.trustStoreType=bcfks{code}
The goal of ticket is to make Oozie capable of setting _keyStoreType_ and
_trustStoreType_ in oozie-site.xml if it's not already set by the user.
was:The goal of ticket is to make Oozie capable of setting _keyStoreType_ and
_trustStoreType_ in oozie-site.xml if it's not already set by the user.
> Oozie should accept a keyStoreType and trustStoreType property in
> oozie-site.xml
> --------------------------------------------------------------------------------
>
> Key: OOZIE-3677
> URL: https://issues.apache.org/jira/browse/OOZIE-3677
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: 5.2.1
> Reporter: Janos Makai
> Assignee: Janos Makai
> Priority: Major
> Attachments: OOZIE-3677-001.patch
>
>
> In scope of making Oozie FIPS compliant, when TLS is enabled, the Oozie
> server expects a JKS KeyStore type even though the following Java system
> properties are being set:
> {code:java}
> -Djavax.net.ssl.keyStoreType=bcfks -Djavax.net.ssl.trustStoreType=bcfks{code}
> The goal of ticket is to make Oozie capable of setting _keyStoreType_ and
> _trustStoreType_ in oozie-site.xml if it's not already set by the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
