You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Selvamohan Neethiraj (JIRA)" <ji...@apache.org> on 2015/06/01 18:47:18 UTC
[jira] [Commented] (RANGER-518) [rolling downgrade] - disable
SHA256 hashing of password to provide a way to test rolling downgrade of
ranger admin downgrade
[ https://issues.apache.org/jira/browse/RANGER-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567558#comment-14567558 ]
Selvamohan Neethiraj commented on RANGER-518:
---------------------------------------------
Patch Approved and committed - 144c2153b7379761a0531d822013460962d55a9f
> [rolling downgrade] - disable SHA256 hashing of password to provide a way to test rolling downgrade of ranger admin downgrade
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-518
> URL: https://issues.apache.org/jira/browse/RANGER-518
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.5.0
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: 0.5.0
>
> Attachments: RANGER-518.1.patch
>
>
> If a custom property is added "ranger.sha256Password.update.disable" with value true, then MD5 password will not be converted to SHA256 hash.
> Once this is available, it should be set in the Ambari QE automation to add this custom property to test rolling downgrade - with "ranger.sha256Password.update.disable" = "true" before the ranger-admin is started from Ambari.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)