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

Hudson commented on AMBARI-14153:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #3963 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3963/])
AMBARI-14153. [Ranger's smart configs] Group User Map Sync should not (jaimin: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e62e8eaa30b7d725a006773e197378ea9e8c797f])
* 
ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/themes/theme_version_2.json
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-ugsync-site.xml


> [Ranger's smart configs] Group User Map Sync should not drive user attributes 
> in usersync config
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14153
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14153
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-14153.1.patch, AMBARI-14153.patch
>
>
> Steps to reproduce:
> 1. Login to Ambari
> 2. Go to Ranger --> Config --> Ranger User Info tab.
> 3. Enable Ranger UserSync and go to User Configs
> 4. Only after enabling Group User Map Sync, the user properties are shown and 
> expected to be filled in. This needs to be changed. Move "Group User Map 
> Sync" property as the last property on the user Configs tab and don't make 
> the user properties depend on this flag.



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

Reply via email to