[jira] [Commented] (AMBARI-13653) Ranger authentication method when updated via recommendation API doe not change the related accordion

["Oleg Nechiporenko (JIRA)" <ji...@apache.org>]

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

Oleg Nechiporenko commented on AMBARI-13653:
--------------------------------------------

+1 for patch

> Ranger authentication method when updated via recommendation API doe not change the related accordion
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13653
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13653
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.3
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13653.patch
>
>
> STR:
> Change Sync Source on Ranger User Info tab to LDAP/AD.
> This changes ranger authentication method in Ranger Settings section under Advanced tab to LDAP. This updated id done via recommendation API
> Expected Result: With the update of Ranger authentication method to LDAP, below accordion should change to "LDAP Settings" as it happens when ranger authentication method is directly changed. 
> Actual Result: Accordion doesn't change. The fix should be generic to address the issue in both HDP-2.2 and HDP-2.3 clusters which has different property name and file names in which property belongs



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