ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11058) Check oozie.https properties to generate oozie war -secure
Date Tue, 12 May 2015 13:31:59 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539827#comment-14539827
] 

Jonathan Hurley commented on AMBARI-11058:
------------------------------------------

{code:python}
+if 'oozie.https.port' in config['configurations']['oozie-site'] or 'oozie.https.keystore.file'
in config['configurations']['oozie-site'] or 'oozie.https.keystore.pass' in config['configurations']['oozie-site']
{code}

In some other services, it's possible to have keys that indicate SSL without actually having
it enabled. Core hadoop (HDFS/YARN) does this. So, just because those keys are present doesn't
mean SSL is enabled. Is this the case for Oozie? That their presence forces it to be enabled?


> Check oozie.https properties to generate oozie war -secure
> ----------------------------------------------------------
>
>                 Key: AMBARI-11058
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11058
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 1.2.1
>
>         Attachments: AMBARI-11058.patch
>
>
> We should trigger a -secure prepare-war step if we notice any oozie.https.* properties
added in the Custom oozie-site.
> {code}
> oozie.https.port=11443
> oozie.https.keystore.file=/home/oozie/.keystore
> oozie.https.keystore.pass=password
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message