ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-12146) Ambari JAAS configuration removed after 2.0.1 to 2.1 upgrade
Date Thu, 25 Jun 2015 17:19:05 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-12146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmytro Sen updated AMBARI-12146:
--------------------------------
    Attachment: AMBARI-12146.patch

> Ambari JAAS configuration removed after 2.0.1 to 2.1 upgrade
> ------------------------------------------------------------
>
>                 Key: AMBARI-12146
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12146
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12146.patch
>
>
> After upgrading from Ambari 2.0.1 with SPNEGO configured, and JAAS configured through
ambari-server setup-security to 2.1.0-1158, after the upgrade the JAAS settings are not retained
so there are multiple UI issues as SPNEGO is in use and prevents Ambari from accessing JMX
endpoints without authentication:
> *Steps to reproduce*
> * Install Ambari 2.0.1 with HDP 2.2.6
> * Configure SPNEGO
> * Configure Ambari's JAAS using ambari-server setup-security
> * Upgrade to Ambari 2.1.0-1158
> * Start services
> * Notice the JAAS settings are not retained and HDFS Summary screen is not accurate



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

Mime
View raw message