You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jeff Sposetti (JIRA)" <ji...@apache.org> on 2014/04/28 23:11:15 UTC
[jira] [Commented] (AMBARI-5602) Configs.sh doesn't work after
https is enable on Ambari-server
[ https://issues.apache.org/jira/browse/AMBARI-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983542#comment-13983542 ]
Jeff Sposetti commented on AMBARI-5602:
---------------------------------------
Hi, Is this covered + implemented with this JIRA? Please take a look.
https://issues.apache.org/jira/browse/AMBARI-5527
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/scripts/configs.sh
Thanks.
> Configs.sh doesn't work after https is enable on Ambari-server
> --------------------------------------------------------------
>
> Key: AMBARI-5602
> URL: https://issues.apache.org/jira/browse/AMBARI-5602
> Project: Ambari
> Issue Type: Bug
> Components: site
> Affects Versions: 1.5.0
> Reporter: Kenny Zhang
> Attachments: configs_https.sh
>
>
> PROBLEM: After https is enabled on ambari-server, the original configs.sh will not work to make any configuration change. Attached the configs_https.sh as a workaround to either use a certificate by specifying '-cert' for a secure SSL connection or use a insecure connection by default.
--
This message was sent by Atlassian JIRA
(v6.2#6252)