You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Ramesh Mani (Jira)" <ji...@apache.org> on 2024/12/13 20:28:00 UTC

[jira] [Updated] (RANGER-4984) Ranger "Federated User" enum order should be correct to avoid potential failure in Ranger Admin

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

Ramesh Mani updated RANGER-4984:
--------------------------------
    Fix Version/s: 3.0.0

> Ranger "Federated User" enum order should be correct to avoid potential failure in Ranger Admin 
> ------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-4984
>                 URL: https://issues.apache.org/jira/browse/RANGER-4984
>             Project: Ranger
>          Issue Type: Improvement
>          Components: Ranger
>    Affects Versions: 3.0.0, 2.6.0
>            Reporter: Ramesh Mani
>            Assignee: Ramesh Mani
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: 0001-RANGER-4984-Ranger-Federated-User-enum-order-should-.patch
>
>
> Ranger "Federated User" enum order should be correct to avoid potential failure in Ranger Admin . Currently the enum USER_FEDERATED is replaced the USER_AD enum. Even though USER_AD not used any where in Ranger is better to avoid replacing and have a new Enum for Federated User.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)