[jira] [Updated] (RANGER-518) [rolling downgrade] - disable SHA256 hashing of password to provide a way to test rolling downgrade of ranger admin downgrade

["Gautam Borad (JIRA)" <ji...@apache.org>]

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

Gautam Borad updated RANGER-518:
--------------------------------
    Attachment: RANGER-518.patch

> [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.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)