[
https://issues.apache.org/jira/browse/AMBARI-13765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-13765:
---------------------------------------
Description:
*STR:*
# Deploy Ranger service with default settings
# After installation go to Ranger->config->Ranger User Info page
# Change "Enable User Sync" toggle to "Yes"
# Save the configuration. This will create another config version for Ranger
# Compare current config version with the presious one
# Apart from "Enable User Sync" property change which belongs to
ranger-ugsync-site.xml, all other properties which are marked as PASSWORD type
in ranger-ugsync-site.xml are changed and appears in the compare view of the
config versions.
*Fix:*
0) Do not show password fields in compare view (mask them out, since they would
always be a difference even if there was no change).
1) In the Ambari Web UI, on any password tooltip, append "\<br\>For security
purposes, password changes will not be shown in configuration version
comparisons"
2) When someone goes to save a config version, in the Save Configuration
dialog, IF the change includes a password change, include this "This
configuration change includes a password change. The password change will be
saved but for security purposes, password changes will not be shown in
configuration version comparisons."
3) The Notes field should be pre-filled with "Password change" if there is a
password change.
was:
*STR:*
# Deploy Ranger service with default settings
# After installation go to Ranger->config->Ranger User Info page
# Change "Enable User Sync" toggle to "Yes"
# Save the configuration. This will create another config version for Ranger
# Compare current config version with the presious one
# Apart from "Enable User Sync" property change which belongs to
ranger-ugsync-site.xml, all other properties which are marked as PASSWORD type
in ranger-ugsync-site.xml are changed and appears in the compare view of the
config versions.
> Encrypted value of the password is changed even when the value is not changed
> by the user
> -----------------------------------------------------------------------------------------
>
> Key: AMBARI-13765
> URL: https://issues.apache.org/jira/browse/AMBARI-13765
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Priority: Critical
> Fix For: 2.1.3
>
>
> *STR:*
> # Deploy Ranger service with default settings
> # After installation go to Ranger->config->Ranger User Info page
> # Change "Enable User Sync" toggle to "Yes"
> # Save the configuration. This will create another config version for Ranger
> # Compare current config version with the presious one
> # Apart from "Enable User Sync" property change which belongs to
> ranger-ugsync-site.xml, all other properties which are marked as PASSWORD
> type in ranger-ugsync-site.xml are changed and appears in the compare view
> of the config versions.
> *Fix:*
> 0) Do not show password fields in compare view (mask them out, since they
> would always be a difference even if there was no change).
> 1) In the Ambari Web UI, on any password tooltip, append "\<br\>For security
> purposes, password changes will not be shown in configuration version
> comparisons"
> 2) When someone goes to save a config version, in the Save Configuration
> dialog, IF the change includes a password change, include this "This
> configuration change includes a password change. The password change will be
> saved but for security purposes, password changes will not be shown in
> configuration version comparisons."
> 3) The Notes field should be pre-filled with "Password change" if there is a
> password change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
