You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2015/08/26 22:49:18 UTC
[jira] [Updated] (AMBARI-12435) oozie prepare-war secure not
executed after disabling and re-enabling HTTPS
[ https://issues.apache.org/jira/browse/AMBARI-12435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nate Cole updated AMBARI-12435:
-------------------------------
Fix Version/s: (was: 2.1.1)
2.1.2
> oozie prepare-war secure not executed after disabling and re-enabling HTTPS
> ---------------------------------------------------------------------------
>
> Key: AMBARI-12435
> URL: https://issues.apache.org/jira/browse/AMBARI-12435
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Mahadev konar
> Fix For: 2.1.2
>
>
> After enabling HTTPS for Oozie, removing the parameters to disable and reenable security does not work. This issue is more easily reproducible like below
> Instead of all the required steps when only 2 of the env parameters are changed - then Ambari sets HTTP port to the HTTPS port and oozie usage fails with Plaintext message to a SSL port
> Any attempt to reenable security fails
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)