[jira] [Updated] (RANGER-3920) When sync'ing users from Ldap, intermittent User/Group/UserGroup membership is missing
[ https://issues.apache.org/jira/browse/RANGER-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-3920: - Description: Problem Statement: Currently, Usersync sync's users/groups/usergroup in batches. In doing so, the user/group/usergroup at the end of the batch is not sync'ed. For example consider batch is of size 1000, so batch starts from 0-999 and then next batch starts from 1001-1999. So in each batch one user/group/usergroup is missing. was: Problem Statement: Usersync sync's user/group/usergroup membership in batches. For example consider batch is of size 1000. So batch start from 0-999 and next batch starts from 1001-1999. So in each batch one user count missing. > When sync'ing users from Ldap, intermittent User/Group/UserGroup membership > is missing > > > Key: RANGER-3920 > URL: https://issues.apache.org/jira/browse/RANGER-3920 > Project: Ranger > Issue Type: Bug > Components: admin, Ranger, usersync >Reporter: Ankita Sinha >Assignee: Ankita Sinha >Priority: Major > Fix For: 2.4.0 > > > Problem Statement: > Currently, Usersync sync's users/groups/usergroup in batches. In doing so, > the user/group/usergroup at the end of the batch is not sync'ed. > For example consider batch is of size 1000, so batch starts from 0-999 and > then next batch starts from 1001-1999. So in each batch one > user/group/usergroup is missing. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3920) When sync'ing users from Ldap, intermittent User/Group/UserGroup membership is missing
[ https://issues.apache.org/jira/browse/RANGER-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-3920: - Summary: When sync'ing users from Ldap, intermittent User/Group/UserGroup membership is missing (was: In Ldap usersync one User/Group/UserGroup membership is missed in each batch when pushed to ranger) > When sync'ing users from Ldap, intermittent User/Group/UserGroup membership > is missing > > > Key: RANGER-3920 > URL: https://issues.apache.org/jira/browse/RANGER-3920 > Project: Ranger > Issue Type: Bug > Components: admin, Ranger, usersync >Reporter: Ankita Sinha >Assignee: Ankita Sinha >Priority: Major > Fix For: 2.4.0 > > > Problem Statement: > Usersync sync's user/group/usergroup membership in batches. For example > consider batch is of size 1000. So batch start from 0-999 and next batch > starts from 1001-1999. So in each batch one user count missing. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3920) In Ldap usersync one User/Group/UserGroup membership is missed in each batch when pushed to ranger
[ https://issues.apache.org/jira/browse/RANGER-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-3920: - Description: Problem Statement: Usersync sync's user/group/usergroup membership in batches. For example consider batch is of size 1000. So batch start from 0-999 and next batch starts from 1001-1999. So in each batch one user count missing. was:In Ldap usersync one User/Group/UserGroup membership is missed in each batch when pushed to ranger > In Ldap usersync one User/Group/UserGroup membership is missed in each batch > when pushed to ranger > -- > > Key: RANGER-3920 > URL: https://issues.apache.org/jira/browse/RANGER-3920 > Project: Ranger > Issue Type: Bug > Components: admin, Ranger, usersync >Reporter: Ankita Sinha >Assignee: Ankita Sinha >Priority: Major > Fix For: 2.4.0 > > > Problem Statement: > Usersync sync's user/group/usergroup membership in batches. For example > consider batch is of size 1000. So batch start from 0-999 and next batch > starts from 1001-1999. So in each batch one user count missing. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-3920) In Ldap usersync one User/Group/UserGroup membership is missed in each batch when pushed to ranger
Ankita Sinha created RANGER-3920: Summary: In Ldap usersync one User/Group/UserGroup membership is missed in each batch when pushed to ranger Key: RANGER-3920 URL: https://issues.apache.org/jira/browse/RANGER-3920 Project: Ranger Issue Type: Bug Components: admin, Ranger, usersync Reporter: Ankita Sinha Assignee: Ankita Sinha Fix For: 2.4.0 In Ldap usersync one User/Group/UserGroup membership is missed in each batch when pushed to ranger -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3621) Optimise Tag/Policy iterator
[
https://issues.apache.org/jira/browse/RANGER-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankita Sinha updated RANGER-3621:
-
Description:
Optimise the logic of Tag and service-policies cache iterator
{+}_Problem Statement_{+}:
Tags/policies in the iterator are not freed till the whole processing of all
Tags/policies are done. So, in the case where there are lot of tag/policies,
the performance can be impacted as the large number of tags/policies are held
by iterator for long time. This causes performance degradation while retrieving
the tags from db.
{+}_Solution_{+}:
The individual tag/policy as soon as it is processed should be removed from the
iterator.
was:
Optimise the logic of Tag iterator
{+}_Problem Statement_{+}:
Tags in the iterator are not freed till the whole processing of all Tags are
done. So, in the case where there are lot of tag, the performance can be
impacted as the large number of tags are held by iterator for long time. This
causes performance degradation while retrieving the tags from db.
{+}_Solution_{+}:
The individual tag as soon as it is processed should be removed from the
iterator.
> Optimise Tag/Policy iterator
> --
>
> Key: RANGER-3621
> URL: https://issues.apache.org/jira/browse/RANGER-3621
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Ankita Sinha
>Assignee: Ankita Sinha
>Priority: Major
> Attachments: RANGER-3621-Optimise-Tag-iterator.patch
>
>
> Optimise the logic of Tag and service-policies cache iterator
> {+}_Problem Statement_{+}:
> Tags/policies in the iterator are not freed till the whole processing of all
> Tags/policies are done. So, in the case where there are lot of tag/policies,
> the performance can be impacted as the large number of tags/policies are held
> by iterator for long time. This causes performance degradation while
> retrieving the tags from db.
> {+}_Solution_{+}:
> The individual tag/policy as soon as it is processed should be removed from
> the iterator.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (RANGER-3621) Optimise Tag/Policy iterator
[
https://issues.apache.org/jira/browse/RANGER-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankita Sinha updated RANGER-3621:
-
Summary: Optimise Tag/Policy iterator(was: Optimise Tag iterator )
> Optimise Tag/Policy iterator
> --
>
> Key: RANGER-3621
> URL: https://issues.apache.org/jira/browse/RANGER-3621
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Ankita Sinha
>Assignee: Ankita Sinha
>Priority: Major
> Attachments: RANGER-3621-Optimise-Tag-iterator.patch
>
>
> Optimise the logic of Tag iterator
> {+}_Problem Statement_{+}:
> Tags in the iterator are not freed till the whole processing of all Tags are
> done. So, in the case where there are lot of tag, the performance can be
> impacted as the large number of tags are held by iterator for long time. This
> causes performance degradation while retrieving the tags from db.
> {+}_Solution_{+}:
> The individual tag as soon as it is processed should be removed from the
> iterator.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (RANGER-3625) Update isDebugEnable condition in RangerHiveAuthorizer
Ankita Sinha created RANGER-3625:
Summary: Update isDebugEnable condition in RangerHiveAuthorizer
Key: RANGER-3625
URL: https://issues.apache.org/jira/browse/RANGER-3625
Project: Ranger
Issue Type: Bug
Components: Ranger
Affects Versions: 2.2.0
Reporter: Ankita Sinha
Assignee: Ankita Sinha
{+}_Problem Statement_{+}:
In RangerHiveAuthorizer, the Logger isDebugEnabled condition needs to be updated
{code:java}
else if (!result.getIsAllowed()) {
if (!LOG.isDebugEnabled()) {
String path =
resource.getAsString();
LOG.debug(String.format("filterListCmdObjects: Permission denied: user [%s]
does not have [%s] privilege on [%s]. resource[%s], request[%s], result[%s]",
user,
request.getHiveAccessType().name(), path, resource, request, result));
} {code}
here in above code the condition check is "!LOG.isDebugEnabled()" and log is
logged at Debug level which will never get log.
{+}_Solution_{+}:
The condition "{*}if (!LOG.isDebugEnabled()){*}" should be replaced by *"if
(LOG.isDebugEnabled())"*
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (RANGER-3625) Update isDebugEnable condition in RangerHiveAuthorizer
[
https://issues.apache.org/jira/browse/RANGER-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankita Sinha updated RANGER-3625:
-
Attachment: RANGER-3625-Update-isDebugEnable-condition-in-Ranger.patch
> Update isDebugEnable condition in RangerHiveAuthorizer
> --
>
> Key: RANGER-3625
> URL: https://issues.apache.org/jira/browse/RANGER-3625
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Ankita Sinha
>Assignee: Ankita Sinha
>Priority: Trivial
> Attachments:
> RANGER-3625-Update-isDebugEnable-condition-in-Ranger.patch
>
>
> {+}_Problem Statement_{+}:
> In RangerHiveAuthorizer, the Logger isDebugEnabled condition needs to be
> updated
> {code:java}
> else if (!result.getIsAllowed()) {
> if (!LOG.isDebugEnabled()) {
> String path =
> resource.getAsString();
>
> LOG.debug(String.format("filterListCmdObjects: Permission denied: user [%s]
> does not have [%s] privilege on [%s]. resource[%s], request[%s], result[%s]",
> user,
> request.getHiveAccessType().name(), path, resource, request, result));
> } {code}
> here in above code the condition check is "!LOG.isDebugEnabled()" and log is
> logged at Debug level which will never get log.
> {+}_Solution_{+}:
> The condition "{*}if (!LOG.isDebugEnabled()){*}" should be replaced by *"if
> (LOG.isDebugEnabled())"*
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (RANGER-3621) Optimise Tag iterator
[
https://issues.apache.org/jira/browse/RANGER-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankita Sinha updated RANGER-3621:
-
Attachment: RANGER-3621-Optimise-Tag-iterator.patch
> Optimise Tag iterator
> ---
>
> Key: RANGER-3621
> URL: https://issues.apache.org/jira/browse/RANGER-3621
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Ankita Sinha
>Assignee: Ankita Sinha
>Priority: Major
> Attachments: RANGER-3621-Optimise-Tag-iterator.patch
>
>
> Optimise the logic of Tag iterator
> {+}_Problem Statement_{+}:
> Tags in the iterator are not freed till the whole processing of all Tags are
> done. So, in the case where there are lot of tag, the performance can be
> impacted as the large number of tags are held by iterator for long time. This
> causes performance degradation while retrieving the tags from db.
> {+}_Solution_{+}:
> The individual tag as soon as it is processed should be removed from the
> iterator.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (RANGER-3621) Optimise Tag iterator
Ankita Sinha created RANGER-3621:
Summary: Optimise Tag iterator
Key: RANGER-3621
URL: https://issues.apache.org/jira/browse/RANGER-3621
Project: Ranger
Issue Type: Improvement
Components: Ranger
Affects Versions: 2.2.0
Reporter: Ankita Sinha
Assignee: Ankita Sinha
Optimise the logic of Tag iterator
{+}_Problem Statement_{+}:
Tags in the iterator are not freed till the whole processing of all Tags are
done. So, in the case where there are lot of tag, the performance can be
impacted as the large number of tags are held by iterator for long time. This
causes performance degradation while retrieving the tags from db.
{+}_Solution_{+}:
The individual tag as soon as it is processed should be removed from the
iterator.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-2331: - Attachment: (was: RANGER-2331-ranger-0.7.patch) > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Ankita Sinha >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha reassigned RANGER-2331: Assignee: Gautam Borad (was: Ankita Sinha) > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Gautam Borad >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-2331: - Attachment: (was: RANGER-2331-01.path) > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Ankita Sinha >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-2331: - Attachment: RANGER-2331-ranger-0.7.patch > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Ankita Sinha >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331-01.path, RANGER-2331-ranger-0.7.patch, > RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-2331: - Attachment: RANGER-2331-01.path > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Ankita Sinha >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331-01.path, RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha reassigned RANGER-2331: Assignee: Ankita Sinha (was: bhavik patel) > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Ankita Sinha >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1945) Save Service would add dirty user when current user is admin
[ https://issues.apache.org/jira/browse/RANGER-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312457#comment-16312457 ] Ankita Sinha commented on RANGER-1945: -- The user needs to be created, because in case of Secure kerberos environment after the authentication is successful will need that user in our DB to do any operations. So any user which is authenticated successfully will be created in Ranger. > Save Service would add dirty user when current user is admin > > > Key: RANGER-1945 > URL: https://issues.apache.org/jira/browse/RANGER-1945 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.6.3 >Reporter: chuanjie.duan > Attachments: RANGER-1945.001.patch > > > When user actually is not exist and current user is admin, "save" operation > would still add user in the backend. It would be a dirty data and obscure > operation(operator maybe doesn't know). And I sync user from ldap, both of > them mark external user, it's hard to distinguish. I suggest don't create > user whenever current is admin or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (RANGER-1759) Ranger KMS and Ranger Admin startup failed at credentialapi.buildks with java.lang.NoClassDefFoundError: org/codehaus/stax2/XMLInputFactory2
[
https://issues.apache.org/jira/browse/RANGER-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankita Sinha resolved RANGER-1759.
--
Resolution: Auto Closed
> Ranger KMS and Ranger Admin startup failed at credentialapi.buildks with
> java.lang.NoClassDefFoundError: org/codehaus/stax2/XMLInputFactory2
>
>
> Key: RANGER-1759
> URL: https://issues.apache.org/jira/browse/RANGER-1759
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: master, 0.7.1
>Reporter: Ankita Sinha
>Assignee: Ankita Sinha
> Fix For: master, 0.7.1
>
> Attachments: RANGER-1759_07.patch, RANGER-1759_master.patch
>
>
> Ranger KMS and Ranger Admin startup failed with
> java.lang.NoClassDefFoundError: org/codehaus/stax2/XMLInputFactory2.
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/codehaus/stax2/XMLInputFactory2
> at
> org.apache.ranger.credentialapi.CredentialReader.getDecryptedString(CredentialReader.java:38)
> at
> org.apache.ranger.credentialapi.buildks.createCredential(buildks.java:88)
> at org.apache.ranger.credentialapi.buildks.main(buildks.java:40)
> Caused by: java.lang.ClassNotFoundException:
> org.codehaus.stax2.XMLInputFactory2
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (RANGER-1759) Ranger KMS and Ranger Admin startup failed at credentialapi.buildks with java.lang.NoClassDefFoundError: org/codehaus/stax2/XMLInputFactory2
[
https://issues.apache.org/jira/browse/RANGER-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankita Sinha updated RANGER-1759:
-
Attachment: RANGER-1759_07.patch
RANGER-1759_master.patch
> Ranger KMS and Ranger Admin startup failed at credentialapi.buildks with
> java.lang.NoClassDefFoundError: org/codehaus/stax2/XMLInputFactory2
>
>
> Key: RANGER-1759
> URL: https://issues.apache.org/jira/browse/RANGER-1759
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: master, 0.7.1
>Reporter: Ankita Sinha
>Assignee: Ankita Sinha
> Fix For: master, 0.7.1
>
> Attachments: RANGER-1759_07.patch, RANGER-1759_master.patch
>
>
> Ranger KMS and Ranger Admin startup failed with
> java.lang.NoClassDefFoundError: org/codehaus/stax2/XMLInputFactory2.
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/codehaus/stax2/XMLInputFactory2
> at
> org.apache.ranger.credentialapi.CredentialReader.getDecryptedString(CredentialReader.java:38)
> at
> org.apache.ranger.credentialapi.buildks.createCredential(buildks.java:88)
> at org.apache.ranger.credentialapi.buildks.main(buildks.java:40)
> Caused by: java.lang.ClassNotFoundException:
> org.codehaus.stax2.XMLInputFactory2
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (RANGER-1759) Ranger KMS and Ranger Admin startup failed at credentialapi.buildks with java.lang.NoClassDefFoundError: org/codehaus/stax2/XMLInputFactory2
Ankita Sinha created RANGER-1759:
Summary: Ranger KMS and Ranger Admin startup failed at
credentialapi.buildks with java.lang.NoClassDefFoundError:
org/codehaus/stax2/XMLInputFactory2
Key: RANGER-1759
URL: https://issues.apache.org/jira/browse/RANGER-1759
Project: Ranger
Issue Type: Bug
Components: Ranger
Affects Versions: 0.7.1, master
Reporter: Ankita Sinha
Assignee: Ankita Sinha
Fix For: master, 0.7.1
Ranger KMS and Ranger Admin startup failed with
java.lang.NoClassDefFoundError: org/codehaus/stax2/XMLInputFactory2.
{code}
Exception in thread "main" java.lang.NoClassDefFoundError:
org/codehaus/stax2/XMLInputFactory2
at
org.apache.ranger.credentialapi.CredentialReader.getDecryptedString(CredentialReader.java:38)
at
org.apache.ranger.credentialapi.buildks.createCredential(buildks.java:88)
at org.apache.ranger.credentialapi.buildks.main(buildks.java:40)
Caused by: java.lang.ClassNotFoundException: org.codehaus.stax2.XMLInputFactory2
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 3 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (RANGER-1705) Good coding practice in Ranger recommended by static code analysis
[ https://issues.apache.org/jira/browse/RANGER-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138009#comment-16138009 ] Ankita Sinha commented on RANGER-1705: -- Committed to master : https://github.com/apache/ranger/commit/02c094393f40b209800f740a1ca8eaa8f7f4e43a Committed to ranger-0.7 : https://github.com/apache/ranger/commit/b85c312b1e34890a9f0cb1d16b3e254452ec7a3c > Good coding practice in Ranger recommended by static code analysis > -- > > Key: RANGER-1705 > URL: https://issues.apache.org/jira/browse/RANGER-1705 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master, 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: master, 0.7.1 > > Attachments: RANGER-1705.patch > > > Good coding practice in Ranger recommended by static code analysis on the > last commit made. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.
[ https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103176#comment-16103176 ] Ankita Sinha commented on RANGER-1690: -- Committed to master : https://github.com/apache/ranger/commit/7d5d00c15d4fdde8d57182dc67ec05b883474191 > Ranger usersync created error users. Ranger usersync got System Virtual User > Group Name instead of real group name when built the unix user list. > -- > > Key: RANGER-1690 > URL: https://issues.apache.org/jira/browse/RANGER-1690 > Project: Ranger > Issue Type: Bug > Components: usersync >Reporter: peng.jianhua >Assignee: Ankita Sinha > Labels: patch > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1690-Ranger-usersync-created-error-users.-Ran.patch, > RANGER-1690.patch > > > The ranger.usersync.unix.minGroupId is not set default value. Like > ranger.usersync.unix.minUserId, it should be set default value. Following > variable equals to 0 when built the unix user list. > minimumGroupId=Integer.parseInt(config.getMinGroupId()); > Ranger usersync may get System Virtual User Group Name instead of real group > name. > if (numGroupId < minimumGroupId) > continue; > String groupName = groupId2groupNameMap.get(gid); > This result is that the Ranger usersync created error users. > http://www.archivum.info/debian-bugs-clo...@lists.debian.org/2006-03/03888/Bug-333706-marked-as-done-(useradd-lacks-r-option).html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.
[ https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103003#comment-16103003 ] Ankita Sinha edited comment on RANGER-1690 at 7/27/17 9:39 AM: --- Hi [~peng.jianhua], the setup is breaking due to extra character at the end of the line in ranger-ugsync-default.xml. I am attaching the patch for the same in this jira and raised the [review request|https://reviews.apache.org/r/61175/diff/1#index_header]. Can you please review. was (Author: ankita.sinha): Hi [~peng.jianhua], the setup is breaking due to extra character at the end of the line in ranger-ugsync-default.xml. I am attaching the patch for the same in this jira and raise the [review request|https://reviews.apache.org/r/61175/diff/1#index_header]. Can you please review. > Ranger usersync created error users. Ranger usersync got System Virtual User > Group Name instead of real group name when built the unix user list. > -- > > Key: RANGER-1690 > URL: https://issues.apache.org/jira/browse/RANGER-1690 > Project: Ranger > Issue Type: Bug > Components: usersync >Reporter: peng.jianhua >Assignee: Ankita Sinha > Labels: patch > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1690-Ranger-usersync-created-error-users.-Ran.patch, > RANGER-1690.patch > > > The ranger.usersync.unix.minGroupId is not set default value. Like > ranger.usersync.unix.minUserId, it should be set default value. Following > variable equals to 0 when built the unix user list. > minimumGroupId=Integer.parseInt(config.getMinGroupId()); > Ranger usersync may get System Virtual User Group Name instead of real group > name. > if (numGroupId < minimumGroupId) > continue; > String groupName = groupId2groupNameMap.get(gid); > This result is that the Ranger usersync created error users. > http://www.archivum.info/debian-bugs-clo...@lists.debian.org/2006-03/03888/Bug-333706-marked-as-done-(useradd-lacks-r-option).html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.
[ https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha reassigned RANGER-1690: Assignee: Ankita Sinha (was: peng.jianhua) > Ranger usersync created error users. Ranger usersync got System Virtual User > Group Name instead of real group name when built the unix user list. > -- > > Key: RANGER-1690 > URL: https://issues.apache.org/jira/browse/RANGER-1690 > Project: Ranger > Issue Type: Bug > Components: usersync >Reporter: peng.jianhua >Assignee: Ankita Sinha > Labels: patch > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1690-Ranger-usersync-created-error-users.-Ran.patch, > RANGER-1690.patch > > > The ranger.usersync.unix.minGroupId is not set default value. Like > ranger.usersync.unix.minUserId, it should be set default value. Following > variable equals to 0 when built the unix user list. > minimumGroupId=Integer.parseInt(config.getMinGroupId()); > Ranger usersync may get System Virtual User Group Name instead of real group > name. > if (numGroupId < minimumGroupId) > continue; > String groupName = groupId2groupNameMap.get(gid); > This result is that the Ranger usersync created error users. > http://www.archivum.info/debian-bugs-clo...@lists.debian.org/2006-03/03888/Bug-333706-marked-as-done-(useradd-lacks-r-option).html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.
[ https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1690: - Attachment: RANGER-1690.patch > Ranger usersync created error users. Ranger usersync got System Virtual User > Group Name instead of real group name when built the unix user list. > -- > > Key: RANGER-1690 > URL: https://issues.apache.org/jira/browse/RANGER-1690 > Project: Ranger > Issue Type: Bug > Components: usersync >Reporter: peng.jianhua >Assignee: peng.jianhua > Labels: patch > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1690-Ranger-usersync-created-error-users.-Ran.patch, > RANGER-1690.patch > > > The ranger.usersync.unix.minGroupId is not set default value. Like > ranger.usersync.unix.minUserId, it should be set default value. Following > variable equals to 0 when built the unix user list. > minimumGroupId=Integer.parseInt(config.getMinGroupId()); > Ranger usersync may get System Virtual User Group Name instead of real group > name. > if (numGroupId < minimumGroupId) > continue; > String groupName = groupId2groupNameMap.get(gid); > This result is that the Ranger usersync created error users. > http://www.archivum.info/debian-bugs-clo...@lists.debian.org/2006-03/03888/Bug-333706-marked-as-done-(useradd-lacks-r-option).html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.
[ https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103003#comment-16103003 ] Ankita Sinha commented on RANGER-1690: -- Hi [~peng.jianhua], the setup is breaking due to extra character at the end of the line in ranger-ugsync-default.xml. I am attaching the patch for the same in this jira and raise the [review request|https://reviews.apache.org/r/61175/diff/1#index_header]. Can you please review. > Ranger usersync created error users. Ranger usersync got System Virtual User > Group Name instead of real group name when built the unix user list. > -- > > Key: RANGER-1690 > URL: https://issues.apache.org/jira/browse/RANGER-1690 > Project: Ranger > Issue Type: Bug > Components: usersync >Reporter: peng.jianhua >Assignee: peng.jianhua > Labels: patch > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1690-Ranger-usersync-created-error-users.-Ran.patch > > > The ranger.usersync.unix.minGroupId is not set default value. Like > ranger.usersync.unix.minUserId, it should be set default value. Following > variable equals to 0 when built the unix user list. > minimumGroupId=Integer.parseInt(config.getMinGroupId()); > Ranger usersync may get System Virtual User Group Name instead of real group > name. > if (numGroupId < minimumGroupId) > continue; > String groupName = groupId2groupNameMap.get(gid); > This result is that the Ranger usersync created error users. > http://www.archivum.info/debian-bugs-clo...@lists.debian.org/2006-03/03888/Bug-333706-marked-as-done-(useradd-lacks-r-option).html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.
[
https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099861#comment-16099861
]
Ankita Sinha commented on RANGER-1690:
--
[~peng.jianhua], Ranger Usersync setup is failing due to this commit with the
below error
{code}
ranger-1.0.0-SNAPSHOT-usersync# ./setup.sh
INFO: moving [/etc/ranger/usersync/conf/java_home.sh] to
[/etc/ranger/usersync/conf/.java_home.sh.25072017152843] ...
Traceback (most recent call last):
File "./setup.py", line 574, in
main()
File "./setup.py", line 402, in main
defaultProps = getXMLConfigMap(join(confFolderName, defaultSiteXMLFileName))
File "./setup.py", line 155, in getXMLConfigMap
tree = ET.parse(xmlFileName)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 656, in parse
parser.feed(data)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1653, in feed
self._raiseerror(v)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1517, in _raiseerror
raise err
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 22,
column 21
{code}
> Ranger usersync created error users. Ranger usersync got System Virtual User
> Group Name instead of real group name when built the unix user list.
> --
>
> Key: RANGER-1690
> URL: https://issues.apache.org/jira/browse/RANGER-1690
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Labels: patch
> Fix For: 1.0.0
>
> Attachments:
> 0001-RANGER-1690-Ranger-usersync-created-error-users.-Ran.patch
>
>
> The ranger.usersync.unix.minGroupId is not set default value. Like
> ranger.usersync.unix.minUserId, it should be set default value. Following
> variable equals to 0 when built the unix user list.
> minimumGroupId=Integer.parseInt(config.getMinGroupId());
> Ranger usersync may get System Virtual User Group Name instead of real group
> name.
> if (numGroupId < minimumGroupId)
> continue;
> String groupName = groupId2groupNameMap.get(gid);
> This result is that the Ranger usersync created error users.
> http://www.archivum.info/debian-bugs-clo...@lists.debian.org/2006-03/03888/Bug-333706-marked-as-done-(useradd-lacks-r-option).html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.
[ https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha reopened RANGER-1690: -- > Ranger usersync created error users. Ranger usersync got System Virtual User > Group Name instead of real group name when built the unix user list. > -- > > Key: RANGER-1690 > URL: https://issues.apache.org/jira/browse/RANGER-1690 > Project: Ranger > Issue Type: Bug > Components: usersync >Reporter: peng.jianhua >Assignee: peng.jianhua > Labels: patch > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1690-Ranger-usersync-created-error-users.-Ran.patch > > > The ranger.usersync.unix.minGroupId is not set default value. Like > ranger.usersync.unix.minUserId, it should be set default value. Following > variable equals to 0 when built the unix user list. > minimumGroupId=Integer.parseInt(config.getMinGroupId()); > Ranger usersync may get System Virtual User Group Name instead of real group > name. > if (numGroupId < minimumGroupId) > continue; > String groupName = groupId2groupNameMap.get(gid); > This result is that the Ranger usersync created error users. > http://www.archivum.info/debian-bugs-clo...@lists.debian.org/2006-03/03888/Bug-333706-marked-as-done-(useradd-lacks-r-option).html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1705) Good coding practice in Ranger recommended by static code analysis
[ https://issues.apache.org/jira/browse/RANGER-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1705: - Attachment: RANGER-1705.patch > Good coding practice in Ranger recommended by static code analysis > -- > > Key: RANGER-1705 > URL: https://issues.apache.org/jira/browse/RANGER-1705 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master, 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: master, 0.7.1 > > Attachments: RANGER-1705.patch > > > Good coding practice in Ranger recommended by static code analysis on the > last commit made. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1705) Good coding practice in Ranger recommended by static code analysis
Ankita Sinha created RANGER-1705: Summary: Good coding practice in Ranger recommended by static code analysis Key: RANGER-1705 URL: https://issues.apache.org/jira/browse/RANGER-1705 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.1, master Reporter: Ankita Sinha Assignee: Ankita Sinha Fix For: master, 0.7.1 Good coding practice in Ranger recommended by static code analysis on the last commit made. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (RANGER-1638) Improve the password validation from Ranger API
[ https://issues.apache.org/jira/browse/RANGER-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha resolved RANGER-1638. -- Resolution: Fixed > Improve the password validation from Ranger API > --- > > Key: RANGER-1638 > URL: https://issues.apache.org/jira/browse/RANGER-1638 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Mehul Parikh >Assignee: Ankita Sinha > Fix For: 1.0.0, 0.7.2 > > Attachments: RANGER-1638.1.patch, RANGER-1638.patch, RANGER-1638.patch > > > Ranger API should apply password validation in sync with what UI is applying > for all users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1638) Improve the password validation from Ranger API
[ https://issues.apache.org/jira/browse/RANGER-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092523#comment-16092523 ] Ankita Sinha commented on RANGER-1638: -- Committed to master : https://github.com/apache/ranger/commit/55e6d4e1398f27d897795a174a332d6e18642b08 Committed to ranger-0.7 : https://github.com/apache/ranger/commit/61d352fc4c2a14527ccb9f5cd216b8711096c346 > Improve the password validation from Ranger API > --- > > Key: RANGER-1638 > URL: https://issues.apache.org/jira/browse/RANGER-1638 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Mehul Parikh >Assignee: Ankita Sinha > Fix For: 1.0.0, 0.7.2 > > Attachments: RANGER-1638.1.patch, RANGER-1638.patch, RANGER-1638.patch > > > Ranger API should apply password validation in sync with what UI is applying > for all users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (RANGER-1638) Improve the password validation from Ranger API
[ https://issues.apache.org/jira/browse/RANGER-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha reassigned RANGER-1638: Assignee: Ankita Sinha (was: Gautam Borad) > Improve the password validation from Ranger API > --- > > Key: RANGER-1638 > URL: https://issues.apache.org/jira/browse/RANGER-1638 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Mehul Parikh >Assignee: Ankita Sinha > Fix For: 1.0.0, 0.7.2 > > Attachments: RANGER-1638.1.patch, RANGER-1638.patch, RANGER-1638.patch > > > Ranger API should apply password validation in sync with what UI is applying > for all users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1639) Ranger KMS should validate key name before importing into DB
[ https://issues.apache.org/jira/browse/RANGER-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080109#comment-16080109 ] Ankita Sinha commented on RANGER-1639: -- Committed to Master : https://github.com/apache/ranger/commit/b47fe34779beb4be49015ca2f3dfecae7413135a Committed to ranger-0.7 : https://github.com/apache/ranger/commit/50ef5f0fd94f29debb81bffb15d2aefe6dad4381 > Ranger KMS should validate key name before importing into DB > > > Key: RANGER-1639 > URL: https://issues.apache.org/jira/browse/RANGER-1639 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1639_07.patch, RANGER-1639.patch > > > *Actual* : > Ranger KMS does not validate key name before importing into DB. So the > imported key can have special characters in Key name. > *Expected* : > Ranger KMS should validate key name before importing into DB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
[ https://issues.apache.org/jira/browse/RANGER-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065878#comment-16065878 ] Ankita Sinha commented on RANGER-1653: -- Committed to master branch : https://github.com/apache/ranger/commit/fdb74d51f86cc5e464e1beefd910fa3fc73ec45d Committed to ranger-0.7 branch : https://github.com/apache/ranger/commit/8675a2495001404ca5ef5678923cf35999ab2211 > Proxying Ranger UI does not work with Ranger-KnoxSSO > > > Key: RANGER-1653 > URL: https://issues.apache.org/jira/browse/RANGER-1653 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1653_07.patch, RANGER-1653.patch > > > *Actual* : > Ranger is not able to handle forwardable headers when proxying the Ranger UI > and turning on SSO for Ranger. > *Expected* : > Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1639) Ranger KMS should validate key name before importing into DB
[ https://issues.apache.org/jira/browse/RANGER-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1639: - Attachment: RANGER-1639_07.patch > Ranger KMS should validate key name before importing into DB > > > Key: RANGER-1639 > URL: https://issues.apache.org/jira/browse/RANGER-1639 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1639_07.patch, RANGER-1639.patch > > > *Actual* : > Ranger KMS does not validate key name before importing into DB. So the > imported key can have special characters in Key name. > *Expected* : > Ranger KMS should validate key name before importing into DB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1639) Ranger KMS should validate key name before importing into DB
[ https://issues.apache.org/jira/browse/RANGER-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1639: - Attachment: RANGER-1639.patch > Ranger KMS should validate key name before importing into DB > > > Key: RANGER-1639 > URL: https://issues.apache.org/jira/browse/RANGER-1639 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1639.patch > > > *Actual* : > Ranger KMS does not validate key name before importing into DB. So the > imported key can have special characters in Key name. > *Expected* : > Ranger KMS should validate key name before importing into DB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1639) Ranger KMS should validate key name before importing into DB
[ https://issues.apache.org/jira/browse/RANGER-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1639: - Attachment: (was: RANGER-1639.patch) > Ranger KMS should validate key name before importing into DB > > > Key: RANGER-1639 > URL: https://issues.apache.org/jira/browse/RANGER-1639 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > > *Actual* : > Ranger KMS does not validate key name before importing into DB. So the > imported key can have special characters in Key name. > *Expected* : > Ranger KMS should validate key name before importing into DB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
[ https://issues.apache.org/jira/browse/RANGER-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1653: - Attachment: (was: RANGER-1653_07.patch) > Proxying Ranger UI does not work with Ranger-KnoxSSO > > > Key: RANGER-1653 > URL: https://issues.apache.org/jira/browse/RANGER-1653 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1653_07.patch, RANGER-1653.patch > > > *Actual* : > Ranger is not able to handle forwardable headers when proxying the Ranger UI > and turning on SSO for Ranger. > *Expected* : > Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
[ https://issues.apache.org/jira/browse/RANGER-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1653: - Attachment: RANGER-1653.patch > Proxying Ranger UI does not work with Ranger-KnoxSSO > > > Key: RANGER-1653 > URL: https://issues.apache.org/jira/browse/RANGER-1653 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1653_07.patch, RANGER-1653.patch > > > *Actual* : > Ranger is not able to handle forwardable headers when proxying the Ranger UI > and turning on SSO for Ranger. > *Expected* : > Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
[ https://issues.apache.org/jira/browse/RANGER-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1653: - Attachment: (was: RANGER-1653.patch) > Proxying Ranger UI does not work with Ranger-KnoxSSO > > > Key: RANGER-1653 > URL: https://issues.apache.org/jira/browse/RANGER-1653 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1653_07.patch, RANGER-1653.patch > > > *Actual* : > Ranger is not able to handle forwardable headers when proxying the Ranger UI > and turning on SSO for Ranger. > *Expected* : > Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
[ https://issues.apache.org/jira/browse/RANGER-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1653: - Attachment: RANGER-1653_07.patch > Proxying Ranger UI does not work with Ranger-KnoxSSO > > > Key: RANGER-1653 > URL: https://issues.apache.org/jira/browse/RANGER-1653 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1653_07.patch, RANGER-1653.patch > > > *Actual* : > Ranger is not able to handle forwardable headers when proxying the Ranger UI > and turning on SSO for Ranger. > *Expected* : > Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
[ https://issues.apache.org/jira/browse/RANGER-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1653: - Attachment: RANGER-1653.patch > Proxying Ranger UI does not work with Ranger-KnoxSSO > > > Key: RANGER-1653 > URL: https://issues.apache.org/jira/browse/RANGER-1653 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1653.patch > > > *Actual* : > Ranger is not able to handle forwardable headers when proxying the Ranger UI > and turning on SSO for Ranger. > *Expected* : > Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
[ https://issues.apache.org/jira/browse/RANGER-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1653: - Attachment: (was: RANGER-1653.patch) > Proxying Ranger UI does not work with Ranger-KnoxSSO > > > Key: RANGER-1653 > URL: https://issues.apache.org/jira/browse/RANGER-1653 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1653.patch > > > *Actual* : > Ranger is not able to handle forwardable headers when proxying the Ranger UI > and turning on SSO for Ranger. > *Expected* : > Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
[ https://issues.apache.org/jira/browse/RANGER-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1653: - Attachment: (was: RANGER-1653.patch) > Proxying Ranger UI does not work with Ranger-KnoxSSO > > > Key: RANGER-1653 > URL: https://issues.apache.org/jira/browse/RANGER-1653 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1653.patch > > > *Actual* : > Ranger is not able to handle forwardable headers when proxying the Ranger UI > and turning on SSO for Ranger. > *Expected* : > Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
[ https://issues.apache.org/jira/browse/RANGER-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1653: - Attachment: RANGER-1653.patch > Proxying Ranger UI does not work with Ranger-KnoxSSO > > > Key: RANGER-1653 > URL: https://issues.apache.org/jira/browse/RANGER-1653 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1653.patch > > > *Actual* : > Ranger is not able to handle forwardable headers when proxying the Ranger UI > and turning on SSO for Ranger. > *Expected* : > Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
[ https://issues.apache.org/jira/browse/RANGER-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1653: - Attachment: RANGER-1653.patch > Proxying Ranger UI does not work with Ranger-KnoxSSO > > > Key: RANGER-1653 > URL: https://issues.apache.org/jira/browse/RANGER-1653 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1653.patch > > > *Actual* : > Ranger is not able to handle forwardable headers when proxying the Ranger UI > and turning on SSO for Ranger. > *Expected* : > Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1653) Proxying Ranger UI does not work with Ranger-KnoxSSO
Ankita Sinha created RANGER-1653: Summary: Proxying Ranger UI does not work with Ranger-KnoxSSO Key: RANGER-1653 URL: https://issues.apache.org/jira/browse/RANGER-1653 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 1.0.0 Reporter: Ankita Sinha Assignee: Ankita Sinha Fix For: 1.0.0 *Actual* : Ranger is not able to handle forwardable headers when proxying the Ranger UI and turning on SSO for Ranger. *Expected* : Proxying Ranger UI should work with Ranger-KnoxSSO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1582) Support KNOX SSO Token based authentication on Ranger REST API calls
[ https://issues.apache.org/jira/browse/RANGER-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047800#comment-16047800 ] Ankita Sinha commented on RANGER-1582: -- Committed to ranger-0.7 : https://github.com/apache/ranger/commit/d4cf793efd2d5c1604e4404ad12f72252470c1cd > Support KNOX SSO Token based authentication on Ranger REST API calls > > > Key: RANGER-1582 > URL: https://issues.apache.org/jira/browse/RANGER-1582 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1582.patch > > > *Actual* : > Currently Knox SSO is just supported from Ranger UI through web browser. > *Expected* : > Support KNOX SSO Token based authentication on Ranger REST API calls. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1582) Support KNOX SSO Token based authentication on Ranger REST API calls
[ https://issues.apache.org/jira/browse/RANGER-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047786#comment-16047786 ] Ankita Sinha commented on RANGER-1582: -- Committed to master : https://github.com/apache/ranger/commit/9a99e3f41cc2125295058a8fc32e5b9e53bb48a4 > Support KNOX SSO Token based authentication on Ranger REST API calls > > > Key: RANGER-1582 > URL: https://issues.apache.org/jira/browse/RANGER-1582 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1582.patch > > > *Actual* : > Currently Knox SSO is just supported from Ranger UI through web browser. > *Expected* : > Support KNOX SSO Token based authentication on Ranger REST API calls. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1639) Ranger KMS should validate key name before importing into DB
[ https://issues.apache.org/jira/browse/RANGER-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1639: - Attachment: RANGER-1639.patch > Ranger KMS should validate key name before importing into DB > > > Key: RANGER-1639 > URL: https://issues.apache.org/jira/browse/RANGER-1639 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1639.patch > > > *Actual* : > Ranger KMS does not validate key name before importing into DB. So the > imported key can have special characters in Key name. > *Expected* : > Ranger KMS should validate key name before importing into DB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1639) Ranger KMS should validate key name before importing into DB
[ https://issues.apache.org/jira/browse/RANGER-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1639: - Attachment: (was: RANGER-1639.patch) > Ranger KMS should validate key name before importing into DB > > > Key: RANGER-1639 > URL: https://issues.apache.org/jira/browse/RANGER-1639 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > > *Actual* : > Ranger KMS does not validate key name before importing into DB. So the > imported key can have special characters in Key name. > *Expected* : > Ranger KMS should validate key name before importing into DB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1639) Ranger KMS should validate key name before importing into DB
[ https://issues.apache.org/jira/browse/RANGER-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1639: - Attachment: RANGER-1639.patch > Ranger KMS should validate key name before importing into DB > > > Key: RANGER-1639 > URL: https://issues.apache.org/jira/browse/RANGER-1639 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1639.patch > > > *Actual* : > Ranger KMS does not validate key name before importing into DB. So the > imported key can have special characters in Key name. > *Expected* : > Ranger KMS should validate key name before importing into DB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1582) Support KNOX SSO Token based authentication on Ranger REST API calls
[ https://issues.apache.org/jira/browse/RANGER-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1582: - Attachment: (was: RANGER-1582.patch) > Support KNOX SSO Token based authentication on Ranger REST API calls > > > Key: RANGER-1582 > URL: https://issues.apache.org/jira/browse/RANGER-1582 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > > *Actual* : > Currently Knox SSO is just supported from Ranger UI through web browser. > *Expected* : > Support KNOX SSO Token based authentication on Ranger REST API calls. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1639) Ranger KMS should validate key name before importing into DB
Ankita Sinha created RANGER-1639: Summary: Ranger KMS should validate key name before importing into DB Key: RANGER-1639 URL: https://issues.apache.org/jira/browse/RANGER-1639 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 1.0.0 Reporter: Ankita Sinha Assignee: Ankita Sinha Fix For: 1.0.0 *Actual* : Ranger KMS does not validate key name before importing into DB. So the imported key can have special characters in Key name. *Expected* : Ranger KMS should validate key name before importing into DB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1607) Ranger service check failed on SLES11.3 cluster with sslv3 alert handshake failure
[
https://issues.apache.org/jira/browse/RANGER-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021210#comment-16021210
]
Ankita Sinha commented on RANGER-1607:
--
Committed to Master :
https://github.com/apache/ranger/commit/56a93f6e483be0c49e35095f7eb0ea20123628e6
Committed to ranger-0.7 :
https://github.com/apache/ranger/commit/a3c8de04f19b984e16cc8a828ac0c3ac99683e00
> Ranger service check failed on SLES11.3 cluster with sslv3 alert handshake
> failure
> --
>
> Key: RANGER-1607
> URL: https://issues.apache.org/jira/browse/RANGER-1607
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Ankita Sinha
>Assignee: Ankita Sinha
> Fix For: 1.0.0, 0.7.1
>
> Attachments: RANGER-1607.patch
>
>
> On SLES11.3 with JDK 1.7 environment, Ranger admin service check is failing
> with below error :
> {code}
> curl --negotiate -u: -k https://localhost:6182/login.jsp
> curl: (35) error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert
> handshake failure
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1607) Ranger service check failed on SLES11.3 cluster with sslv3 alert handshake failure
[
https://issues.apache.org/jira/browse/RANGER-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankita Sinha updated RANGER-1607:
-
Attachment: RANGER-1607.patch
> Ranger service check failed on SLES11.3 cluster with sslv3 alert handshake
> failure
> --
>
> Key: RANGER-1607
> URL: https://issues.apache.org/jira/browse/RANGER-1607
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Ankita Sinha
>Assignee: Ankita Sinha
> Fix For: 1.0.0, 0.7.1
>
> Attachments: RANGER-1607.patch
>
>
> On SLES11.3 with JDK 1.7 environment, Ranger admin service check is failing
> with below error :
> {code}
> curl --negotiate -u: -k https://localhost:6182/login.jsp
> curl: (35) error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert
> handshake failure
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (RANGER-1607) Ranger service check failed on SLES11.3 cluster with sslv3 alert handshake failure
Ankita Sinha created RANGER-1607:
Summary: Ranger service check failed on SLES11.3 cluster with
sslv3 alert handshake failure
Key: RANGER-1607
URL: https://issues.apache.org/jira/browse/RANGER-1607
Project: Ranger
Issue Type: Bug
Components: Ranger
Reporter: Ankita Sinha
Assignee: Ankita Sinha
Fix For: 1.0.0, 0.7.1
On SLES11.3 with JDK 1.7 environment, Ranger admin service check is failing
with below error :
{code}
curl --negotiate -u: -k https://localhost:6182/login.jsp
curl: (35) error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert
handshake failure
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1582) Support KNOX SSO Token based authentication on Ranger REST API calls
[ https://issues.apache.org/jira/browse/RANGER-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1582: - Attachment: RANGER-1582.patch > Support KNOX SSO Token based authentication on Ranger REST API calls > > > Key: RANGER-1582 > URL: https://issues.apache.org/jira/browse/RANGER-1582 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > Attachments: RANGER-1582.patch > > > *Actual* : > Currently Knox SSO is just supported from Ranger UI through web browser. > *Expected* : > Support KNOX SSO Token based authentication on Ranger REST API calls. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1582) Support KNOX SSO Token based authentication on Ranger REST API calls
[ https://issues.apache.org/jira/browse/RANGER-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1582: - Description: *Actual* : Currently Knox SSO is just supported from Ranger UI through web browser. *Expected* : Support KNOX SSO Token based authentication on Ranger REST API calls. was: Actual : Currently Knox SSO is just supported from Ranger UI through web browser. Expected : Support KNOX SSO Token based authentication on Ranger REST API calls. > Support KNOX SSO Token based authentication on Ranger REST API calls > > > Key: RANGER-1582 > URL: https://issues.apache.org/jira/browse/RANGER-1582 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > > *Actual* : > Currently Knox SSO is just supported from Ranger UI through web browser. > *Expected* : > Support KNOX SSO Token based authentication on Ranger REST API calls. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1582) Support KNOX SSO Token based authentication on Ranger REST API calls
[ https://issues.apache.org/jira/browse/RANGER-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1582: - Description: *Actual : * Currently Knox SSO is just supported from Ranger UI through web browser. *Expected : * Support KNOX SSO Token based authentication on Ranger REST API calls. was: **Actual : ** Currently Knox SSO is just supported from Ranger UI through web browser. **Expected : ** Support KNOX SSO Token based authentication on Ranger REST API calls. > Support KNOX SSO Token based authentication on Ranger REST API calls > > > Key: RANGER-1582 > URL: https://issues.apache.org/jira/browse/RANGER-1582 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > > *Actual : * > Currently Knox SSO is just supported from Ranger UI through web browser. > *Expected : * > Support KNOX SSO Token based authentication on Ranger REST API calls. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1582) Support KNOX SSO Token based authentication on Ranger REST API calls
[ https://issues.apache.org/jira/browse/RANGER-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1582: - Description: Actual : Currently Knox SSO is just supported from Ranger UI through web browser. Expected : Support KNOX SSO Token based authentication on Ranger REST API calls. was: *Actual : * Currently Knox SSO is just supported from Ranger UI through web browser. *Expected : * Support KNOX SSO Token based authentication on Ranger REST API calls. > Support KNOX SSO Token based authentication on Ranger REST API calls > > > Key: RANGER-1582 > URL: https://issues.apache.org/jira/browse/RANGER-1582 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0 > > > Actual : > Currently Knox SSO is just supported from Ranger UI through web browser. > Expected : > Support KNOX SSO Token based authentication on Ranger REST API calls. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1562) HDFS test connection is failing due to null pointer exception
[
https://issues.apache.org/jira/browse/RANGER-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004130#comment-16004130
]
Ankita Sinha commented on RANGER-1562:
--
Committed to Master branch :
https://github.com/apache/ranger/commit/0ba3e129a068cf68ea8c2a77f003e112d0d54e08
Committed to ranger-0.7 branch :
https://github.com/apache/ranger/commit/9aad8d6e7649fe40909a74af8865fff3e28e3ebc
> HDFS test connection is failing due to null pointer exception
> -
>
> Key: RANGER-1562
> URL: https://issues.apache.org/jira/browse/RANGER-1562
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 0.7.1
>Reporter: Deepak Sharma
>Assignee: Ankita Sinha
> Fix For: 0.7.1
>
> Attachments: RANGER-1562.patch
>
>
> HDFS test connection is failing due to null pointer exception:
> {code}
> 2017-05-05 15:36:10,025 [timed-executor-pool-0] INFO
> apache.ranger.services.hdfs.client.HdfsClient (HdfsClient.java:204) - ===>
> HdfsClient.testConnection()
> 2017-05-05 15:36:10,032 [timed-executor-pool-0] ERROR
> org.apache.ranger.biz.ServiceMgr$TimedCallable (ServiceMgr.java:510) -
> TimedCallable.call: Error:java.lang.NullPointerException
> 2017-05-05 15:36:10,035 [http-bio-6182-exec-4] ERROR
> org.apache.ranger.biz.ServiceMgr (ServiceMgr.java:188) - ==>
> ServiceMgr.validateConfig
> Error:org.apache.ranger.plugin.client.HadoopException:
> java.lang.NullPointerException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1562) HDFS test connection is failing due to null pointer exception
[
https://issues.apache.org/jira/browse/RANGER-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankita Sinha updated RANGER-1562:
-
Attachment: RANGER-1562.patch
> HDFS test connection is failing due to null pointer exception
> -
>
> Key: RANGER-1562
> URL: https://issues.apache.org/jira/browse/RANGER-1562
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 0.7.1
>Reporter: Deepak Sharma
>Assignee: Ankita Sinha
> Fix For: 0.7.1
>
> Attachments: RANGER-1562.patch
>
>
> HDFS test connection is failing due to null pointer exception:
> {code}
> 2017-05-05 15:36:10,025 [timed-executor-pool-0] INFO
> apache.ranger.services.hdfs.client.HdfsClient (HdfsClient.java:204) - ===>
> HdfsClient.testConnection()
> 2017-05-05 15:36:10,032 [timed-executor-pool-0] ERROR
> org.apache.ranger.biz.ServiceMgr$TimedCallable (ServiceMgr.java:510) -
> TimedCallable.call: Error:java.lang.NullPointerException
> 2017-05-05 15:36:10,035 [http-bio-6182-exec-4] ERROR
> org.apache.ranger.biz.ServiceMgr (ServiceMgr.java:188) - ==>
> ServiceMgr.validateConfig
> Error:org.apache.ranger.plugin.client.HadoopException:
> java.lang.NullPointerException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (RANGER-1562) HDFS test connection is failing due to null pointer exception
[
https://issues.apache.org/jira/browse/RANGER-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankita Sinha reassigned RANGER-1562:
Assignee: Ankita Sinha
> HDFS test connection is failing due to null pointer exception
> -
>
> Key: RANGER-1562
> URL: https://issues.apache.org/jira/browse/RANGER-1562
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 0.7.1
>Reporter: Deepak Sharma
>Assignee: Ankita Sinha
> Fix For: 0.7.1
>
>
> HDFS test connection is failing due to null pointer exception:
> {code}
> 2017-05-05 15:36:10,025 [timed-executor-pool-0] INFO
> apache.ranger.services.hdfs.client.HdfsClient (HdfsClient.java:204) - ===>
> HdfsClient.testConnection()
> 2017-05-05 15:36:10,032 [timed-executor-pool-0] ERROR
> org.apache.ranger.biz.ServiceMgr$TimedCallable (ServiceMgr.java:510) -
> TimedCallable.call: Error:java.lang.NullPointerException
> 2017-05-05 15:36:10,035 [http-bio-6182-exec-4] ERROR
> org.apache.ranger.biz.ServiceMgr (ServiceMgr.java:188) - ==>
> ServiceMgr.validateConfig
> Error:org.apache.ranger.plugin.client.HadoopException:
> java.lang.NullPointerException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1560) Code Improvement To Follow Best Practices
[ https://issues.apache.org/jira/browse/RANGER-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1560: - Attachment: RANGER-1560.patch > Code Improvement To Follow Best Practices > - > > Key: RANGER-1560 > URL: https://issues.apache.org/jira/browse/RANGER-1560 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1560.patch > > > Code Improvement To Follow Best Practices -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1556) Provide keyadmin user with privileges to read ranger kms audits
[ https://issues.apache.org/jira/browse/RANGER-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1556: - Attachment: RANGER-1556.patch > Provide keyadmin user with privileges to read ranger kms audits > --- > > Key: RANGER-1556 > URL: https://issues.apache.org/jira/browse/RANGER-1556 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1556.patch > > > *Actual* : > To provide keyadmin user privileges for Ranger KMS Audit folder, manually > policy need to be created giving all access rights in HDFS repo > *Expected* : > Need to handle default policy creation in HDFS for keyadmin user to have > access to all access rights for Ranger KMS Audits folder (/ranger/audit/kms) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1556) Provide keyadmin user with privileges to read ranger kms audits
[ https://issues.apache.org/jira/browse/RANGER-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1556: - Description: *Actual* : To provide keyadmin user privileges for Ranger KMS Audit folder, manually policy need to be created giving all access rights in HDFS repo *Expected* : Need to handle default policy creation in HDFS for keyadmin user to have access to all access rights for Ranger KMS Audits folder (/ranger/audit/kms) was: Actual : To provide keyadmin user privileges for Ranger KMS Audit folder, manually policy need to be created giving all access rights in HDFS repo Expected : Need to handle default policy creation in HDFS for keyadmin user to have access to all access rights for Ranger KMS Audits folder (/ranger/audit/kms) > Provide keyadmin user with privileges to read ranger kms audits > --- > > Key: RANGER-1556 > URL: https://issues.apache.org/jira/browse/RANGER-1556 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > > *Actual* : > To provide keyadmin user privileges for Ranger KMS Audit folder, manually > policy need to be created giving all access rights in HDFS repo > *Expected* : > Need to handle default policy creation in HDFS for keyadmin user to have > access to all access rights for Ranger KMS Audits folder (/ranger/audit/kms) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1556) Provide keyadmin user with privileges to read ranger kms audits
Ankita Sinha created RANGER-1556: Summary: Provide keyadmin user with privileges to read ranger kms audits Key: RANGER-1556 URL: https://issues.apache.org/jira/browse/RANGER-1556 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.1 Reporter: Ankita Sinha Assignee: Ankita Sinha Fix For: 0.7.1 Actual : To provide keyadmin user privileges for Ranger KMS Audit folder, manually policy need to be created giving all access rights in HDFS repo Expected : Need to handle default policy creation in HDFS for keyadmin user to have access to all access rights for Ranger KMS Audits folder (/ranger/audit/kms) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1548) Display detailed error messages in Ranger for Audit store issues
[ https://issues.apache.org/jira/browse/RANGER-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1548: - Attachment: RANGER-1548_master.patch > Display detailed error messages in Ranger for Audit store issues > > > Key: RANGER-1548 > URL: https://issues.apache.org/jira/browse/RANGER-1548 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1548_07.patch, RANGER-1548_master.patch > > > Actual : > When audit store is not configured properly or if audit store is down, Ranger > UI shows > "Unable to connect to Audit store !!" > Expected : > To show more informative message if audit store has some issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1548) Display detailed error messages in Ranger for Audit store issues
[ https://issues.apache.org/jira/browse/RANGER-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1548: - Attachment: (was: RANGER-1548_07.patch) > Display detailed error messages in Ranger for Audit store issues > > > Key: RANGER-1548 > URL: https://issues.apache.org/jira/browse/RANGER-1548 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1548_07.patch > > > Actual : > When audit store is not configured properly or if audit store is down, Ranger > UI shows > "Unable to connect to Audit store !!" > Expected : > To show more informative message if audit store has some issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1548) Display detailed error messages in Ranger for Audit store issues
[ https://issues.apache.org/jira/browse/RANGER-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1548: - Attachment: (was: RANGER-1548.patch) > Display detailed error messages in Ranger for Audit store issues > > > Key: RANGER-1548 > URL: https://issues.apache.org/jira/browse/RANGER-1548 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1548_07.patch > > > Actual : > When audit store is not configured properly or if audit store is down, Ranger > UI shows > "Unable to connect to Audit store !!" > Expected : > To show more informative message if audit store has some issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1548) Display detailed error messages in Ranger for Audit store issues
[ https://issues.apache.org/jira/browse/RANGER-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1548: - Attachment: RANGER-1548_07.patch > Display detailed error messages in Ranger for Audit store issues > > > Key: RANGER-1548 > URL: https://issues.apache.org/jira/browse/RANGER-1548 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1548_07.patch, RANGER-1548.patch > > > Actual : > When audit store is not configured properly or if audit store is down, Ranger > UI shows > "Unable to connect to Audit store !!" > Expected : > To show more informative message if audit store has some issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1548) Display detailed error messages in Ranger for Audit store issues
[ https://issues.apache.org/jira/browse/RANGER-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1548: - Attachment: RANGER-1548.patch > Display detailed error messages in Ranger for Audit store issues > > > Key: RANGER-1548 > URL: https://issues.apache.org/jira/browse/RANGER-1548 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1548.patch > > > Actual : > When audit store is not configured properly or if audit store is down, Ranger > UI shows > "Unable to connect to Audit store !!" > Expected : > To show more informative message if audit store has some issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1548) Display detailed error messages in Ranger for Audit store issues
Ankita Sinha created RANGER-1548: Summary: Display detailed error messages in Ranger for Audit store issues Key: RANGER-1548 URL: https://issues.apache.org/jira/browse/RANGER-1548 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.1 Reporter: Ankita Sinha Assignee: Ankita Sinha Fix For: 0.7.1 Actual : When audit store is not configured properly or if audit store is down, Ranger UI shows "Unable to connect to Audit store !!" Expected : To show more informative message if audit store has some issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1483) Ranger hive service definition to use hive metastore directly
[ https://issues.apache.org/jira/browse/RANGER-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983331#comment-15983331 ] Ankita Sinha commented on RANGER-1483: -- Committed to Master branch : https://github.com/apache/ranger/commit/66b258ae951611a4a2862d8f0547071d8d411146 Committed to 0.7 branch : https://github.com/apache/ranger/commit/70dcd590701f581f864ee847f7a28c41620349a8 > Ranger hive service definition to use hive metastore directly > - > > Key: RANGER-1483 > URL: https://issues.apache.org/jira/browse/RANGER-1483 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1483_07.patch, RANGER-1483_Master.patch, > RANGER-1483.patch > > > Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver > to fetch hive db/table info, which is used to populate drop downs while > creating/updating policies. Adding ranger hive service definition to also use > hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1483) Ranger hive service definition to use hive metastore directly
[ https://issues.apache.org/jira/browse/RANGER-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1483: - Attachment: RANGER-1483.patch > Ranger hive service definition to use hive metastore directly > - > > Key: RANGER-1483 > URL: https://issues.apache.org/jira/browse/RANGER-1483 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1483_07.patch, RANGER-1483_Master.patch, > RANGER-1483.patch > > > Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver > to fetch hive db/table info, which is used to populate drop downs while > creating/updating policies. Adding ranger hive service definition to also use > hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1483) Ranger hive service definition to use hive metastore directly
[ https://issues.apache.org/jira/browse/RANGER-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1483: - Attachment: (was: RANGER-1483_master_01.patch) > Ranger hive service definition to use hive metastore directly > - > > Key: RANGER-1483 > URL: https://issues.apache.org/jira/browse/RANGER-1483 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1483_07.patch, RANGER-1483_Master.patch, > RANGER-1483.patch > > > Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver > to fetch hive db/table info, which is used to populate drop downs while > creating/updating policies. Adding ranger hive service definition to also use > hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1483) Ranger hive service definition to use hive metastore directly
[ https://issues.apache.org/jira/browse/RANGER-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1483: - Attachment: RANGER-1483_07_1.patch RANGER-1483_master_01.patch > Ranger hive service definition to use hive metastore directly > - > > Key: RANGER-1483 > URL: https://issues.apache.org/jira/browse/RANGER-1483 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1483_07_1.patch, RANGER-1483_07.patch, > RANGER-1483_master_01.patch, RANGER-1483_Master.patch > > > Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver > to fetch hive db/table info, which is used to populate drop downs while > creating/updating policies. Adding ranger hive service definition to also use > hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (RANGER-1483) Ranger hive service definition to use hive metastore directly
[ https://issues.apache.org/jira/browse/RANGER-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha reopened RANGER-1483: -- > Ranger hive service definition to use hive metastore directly > - > > Key: RANGER-1483 > URL: https://issues.apache.org/jira/browse/RANGER-1483 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1483_07_1.patch, RANGER-1483_07.patch, > RANGER-1483_master_01.patch, RANGER-1483_Master.patch > > > Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver > to fetch hive db/table info, which is used to populate drop downs while > creating/updating policies. Adding ranger hive service definition to also use > hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1483) Ranger hive service definition to use hive metastore directly
[ https://issues.apache.org/jira/browse/RANGER-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15951334#comment-15951334 ] Ankita Sinha commented on RANGER-1483: -- Committed to Master branch : https://github.com/apache/ranger/commit/6cfb01883fb97bd98e5e5b7baacb3cdd85a15b68 Committed to 0.7 branch : https://github.com/apache/ranger/commit/6c0b06252ad670bdbd5ffba93a3b51015308e9ec > Ranger hive service definition to use hive metastore directly > - > > Key: RANGER-1483 > URL: https://issues.apache.org/jira/browse/RANGER-1483 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1483_07.patch, RANGER-1483_Master.patch > > > Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver > to fetch hive db/table info, which is used to populate drop downs while > creating/updating policies. Adding ranger hive service definition to also use > hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1483) Ranger hive service definition to use hive metastore directly
[ https://issues.apache.org/jira/browse/RANGER-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1483: - Attachment: (was: RANGER-1483_07.patch) > Ranger hive service definition to use hive metastore directly > - > > Key: RANGER-1483 > URL: https://issues.apache.org/jira/browse/RANGER-1483 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > > Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver > to fetch hive db/table info, which is used to populate drop downs while > creating/updating policies. Adding ranger hive service definition to also use > hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1483) Ranger hive service definition to use hive metastore directly
[ https://issues.apache.org/jira/browse/RANGER-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1483: - Attachment: (was: RANGER-1483_Master.patch) > Ranger hive service definition to use hive metastore directly > - > > Key: RANGER-1483 > URL: https://issues.apache.org/jira/browse/RANGER-1483 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > > Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver > to fetch hive db/table info, which is used to populate drop downs while > creating/updating policies. Adding ranger hive service definition to also use > hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1483) Ranger hive service definition to use hive metastore directly
[ https://issues.apache.org/jira/browse/RANGER-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948378#comment-15948378 ] Ankita Sinha commented on RANGER-1483: -- [~coheigea], I think RANGER-768 is about Metastore plugin and the DDL-triggered policy changes. This Jira is about providing an optional feature of fetching database/table information from Hive Metastore directly. > Ranger hive service definition to use hive metastore directly > - > > Key: RANGER-1483 > URL: https://issues.apache.org/jira/browse/RANGER-1483 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1483_07.patch, RANGER-1483_Master.patch > > > Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver > to fetch hive db/table info, which is used to populate drop downs while > creating/updating policies. Adding ranger hive service definition to also use > hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1483) Ranger hive service definition to use hive metastore directly
[ https://issues.apache.org/jira/browse/RANGER-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1483: - Attachment: RANGER-1483_07.patch RANGER-1483_Master.patch > Ranger hive service definition to use hive metastore directly > - > > Key: RANGER-1483 > URL: https://issues.apache.org/jira/browse/RANGER-1483 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1483_07.patch, RANGER-1483_Master.patch > > > Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver > to fetch hive db/table info, which is used to populate drop downs while > creating/updating policies. Adding ranger hive service definition to also use > hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1483) Ranger hive service definition to use hive metastore directly
Ankita Sinha created RANGER-1483: Summary: Ranger hive service definition to use hive metastore directly Key: RANGER-1483 URL: https://issues.apache.org/jira/browse/RANGER-1483 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.1 Reporter: Ankita Sinha Assignee: Ankita Sinha Fix For: 0.7.1 Currently, ranger hive service definition uses hiveserver2(hs2) jdbc driver to fetch hive db/table info, which is used to populate drop downs while creating/updating policies. Adding ranger hive service definition to also use hive metastore client which read from hive metastore db. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1453) Ranger KMS failed to start with Exception: More than one Master Key exists
Ankita Sinha created RANGER-1453:
Summary: Ranger KMS failed to start with Exception: More than one
Master Key exists
Key: RANGER-1453
URL: https://issues.apache.org/jira/browse/RANGER-1453
Project: Ranger
Issue Type: Bug
Components: Ranger
Affects Versions: 0.7.0
Reporter: Ankita Sinha
Assignee: Ankita Sinha
Fix For: 0.7.1
Ranger KMS failed to start with Exception: More than one Master Key exists
{code}
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was
removed in 8.0
Mar 07, 2017 7:22:30 AM org.apache.ranger.server.tomcat.EmbeddedServer
loadConfig
SEVERE: Load configuration fail. Reason: java.io.FileNotFoundException:
/usr/hdp/2.6.0.2-4/ranger-kms/ews/ranger-admin-default-site.xml (No such file
or directory)
Mar 07, 2017 7:22:30 AM org.apache.ranger.server.tomcat.EmbeddedServer start
INFO: Webapp file =./webapp, webAppName = /kms
Mar 07, 2017 7:22:30 AM org.apache.ranger.server.tomcat.EmbeddedServer start
INFO: Adding webapp [/kms] = path [./webapp] .
Mar 07, 2017 7:22:30 AM org.apache.ranger.server.tomcat.EmbeddedServer start
INFO: Finished init of webapp [/kms] = path [./webapp].
Mar 07, 2017 7:22:30 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9292"]
Mar 07, 2017 7:22:30 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Tomcat
Mar 07, 2017 7:22:30 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.68
Mar 07, 2017 7:22:30 AM org.apache.catalina.startup.ContextConfig
getDefaultWebXmlFragment
INFO: No global web.xml found
Mar 07, 2017 7:22:36 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug
logging for this logger for a complete list of JARs that were scanned but no
TLDs were found in them. Skipping unneeded JARs during scanning can improve
startup time and JSP compilation time.
log4j:WARN No such property [maxFileSize] in
org.apache.log4j.DailyRollingFileAppender.
log4j:WARN No such property [maxBackupIndex] in
org.apache.log4j.DailyRollingFileAppender.
log4j:WARN No such property [maxBackupIndex] in
org.apache.log4j.DailyRollingFileAppender.
log4j:WARN No such property [maxFileSize] in
org.apache.log4j.DailyRollingFileAppender.
java.lang.Exception: More than one Master Key exists
at
org.apache.hadoop.crypto.key.RangerMasterKey.getEncryptedMK(RangerMasterKey.java:143)
at
org.apache.hadoop.crypto.key.RangerMasterKey.getMasterKey(RangerMasterKey.java:71)
at
org.apache.hadoop.crypto.key.RangerKeyStoreProvider.(RangerKeyStoreProvider.java:106)
at
org.apache.hadoop.crypto.key.RangerKeyStoreProvider$Factory.createProvider(RangerKeyStoreProvider.java:399)
at
org.apache.hadoop.crypto.key.KeyProviderFactory.get(KeyProviderFactory.java:95)
at
org.apache.hadoop.crypto.key.kms.server.KMSWebApp.contextInitialized(KMSWebApp.java:176)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5068)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5584)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
java.lang.Exception: No Master Key Found
at
org.apache.hadoop.crypto.key.RangerMasterKey.getMasterKey(RangerMasterKey.java:75)
at
org.apache.hadoop.crypto.key.RangerKeyStoreProvider.(RangerKeyStoreProvider.java:106)
at
org.apache.hadoop.crypto.key.RangerKeyStoreProvider$Factory.createProvider(RangerKeyStoreProvider.java:399)
at
org.apache.hadoop.crypto.key.KeyProviderFactory.get(KeyProviderFactory.java:95)
at
org.apache.hadoop.crypto.key.kms.server.KMSWebApp.contextInitialized(KMSWebApp.java:176)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5068)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5584)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
[jira] [Commented] (RANGER-1428) In certain scenario user data contains junk email-id
[ https://issues.apache.org/jira/browse/RANGER-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905232#comment-15905232 ] Ankita Sinha commented on RANGER-1428: -- Master branch commit : https://github.com/apache/ranger/commit/910aff0edf48b595a4e86b31d2edfda621d2f9ff Ranger-0.7 branch commit : https://github.com/apache/ranger/commit/852e89cda3f54cf322a695cd511b015f31a335c0 > In certain scenario user data contains junk email-id > > > Key: RANGER-1428 > URL: https://issues.apache.org/jira/browse/RANGER-1428 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1428.patch > > > Description: > Junk email id is displayed in some scenario > Steps to reproduce > When added non-existing user while creating a service, it gets created in > user listing without email id but when same user is deleted it shows some > random data in email field in “User Profile deleted” entry > Steps to follow: > 1. Create a service with non-existing user(user will get created in user > listing) > 2. Now delete that user > 3. Go to Audit-Admin tab and check log for "User Profile deleted", in > email-id field it will show some random data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1428) In certain scenario user data contains junk email-id
[ https://issues.apache.org/jira/browse/RANGER-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1428: - Attachment: RANGER-1428.patch > In certain scenario user data contains junk email-id > > > Key: RANGER-1428 > URL: https://issues.apache.org/jira/browse/RANGER-1428 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1428.patch > > > Description: > Junk email id is displayed in some scenario > Steps to reproduce > When added non-existing user while creating a service, it gets created in > user listing without email id but when same user is deleted it shows some > random data in email field in “User Profile deleted” entry > Steps to follow: > 1. Create a service with non-existing user(user will get created in user > listing) > 2. Now delete that user > 3. Go to Audit-Admin tab and check log for "User Profile deleted", in > email-id field it will show some random data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1428) In certain scenario user data contains junk email-id
[ https://issues.apache.org/jira/browse/RANGER-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1428: - Attachment: (was: RANGER-1428.patch) > In certain scenario user data contains junk email-id > > > Key: RANGER-1428 > URL: https://issues.apache.org/jira/browse/RANGER-1428 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > > Description: > Junk email id is displayed in some scenario > Steps to reproduce > When added non-existing user while creating a service, it gets created in > user listing without email id but when same user is deleted it shows some > random data in email field in “User Profile deleted” entry > Steps to follow: > 1. Create a service with non-existing user(user will get created in user > listing) > 2. Now delete that user > 3. Go to Audit-Admin tab and check log for "User Profile deleted", in > email-id field it will show some random data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1428) In certain scenario user data contains junk email-id
[ https://issues.apache.org/jira/browse/RANGER-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1428: - Attachment: RANGER-1428.patch > In certain scenario user data contains junk email-id > > > Key: RANGER-1428 > URL: https://issues.apache.org/jira/browse/RANGER-1428 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1428.patch > > > Description: > Junk email id is displayed in some scenario > Steps to reproduce > When added non-existing user while creating a service, it gets created in > user listing without email id but when same user is deleted it shows some > random data in email field in “User Profile deleted” entry > Steps to follow: > 1. Create a service with non-existing user(user will get created in user > listing) > 2. Now delete that user > 3. Go to Audit-Admin tab and check log for "User Profile deleted", in > email-id field it will show some random data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1428) In certain scenario user data contains junk email-id
[ https://issues.apache.org/jira/browse/RANGER-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1428: - Attachment: (was: RANGER-1428.patch) > In certain scenario user data contains junk email-id > > > Key: RANGER-1428 > URL: https://issues.apache.org/jira/browse/RANGER-1428 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1428.patch > > > Description: > Junk email id is displayed in some scenario > Steps to reproduce > When added non-existing user while creating a service, it gets created in > user listing without email id but when same user is deleted it shows some > random data in email field in “User Profile deleted” entry > Steps to follow: > 1. Create a service with non-existing user(user will get created in user > listing) > 2. Now delete that user > 3. Go to Audit-Admin tab and check log for "User Profile deleted", in > email-id field it will show some random data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1428) In certain scenario user data contains junk email-id
[ https://issues.apache.org/jira/browse/RANGER-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1428: - Description: Description: Junk email id is displayed in some scenario Steps to reproduce When added non-existing user while creating a service, it gets created in user listing without email id but when same user is deleted it shows some random data in email field in “User Profile deleted” entry Steps to follow: 1. Create a service with non-existing user(user will get created in user listing) 2. Now delete that user 3. Go to Audit-Admin tab and check log for "User Profile deleted", in email-id field it will show some random data was: Description: 1. Junk email id is displayed in some scenario Steps to reproduce point 2 When added non-existing user while creating a service, it gets created in user listing without email id but when same user is deleted it shows some random data in email field in “User Profile deleted” entry Steps to follow: 1. Create a service with non-existing user(user will get created in user listing) 2. Now delete that user 3. Go to Audit-Admin tab and check log for "User Profile deleted", in email-id field it will show some random data > In certain scenario user data contains junk email-id > > > Key: RANGER-1428 > URL: https://issues.apache.org/jira/browse/RANGER-1428 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1428.patch > > > Description: > Junk email id is displayed in some scenario > Steps to reproduce > When added non-existing user while creating a service, it gets created in > user listing without email id but when same user is deleted it shows some > random data in email field in “User Profile deleted” entry > Steps to follow: > 1. Create a service with non-existing user(user will get created in user > listing) > 2. Now delete that user > 3. Go to Audit-Admin tab and check log for "User Profile deleted", in > email-id field it will show some random data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1428) In certain scenario user data contains junk email-id
[ https://issues.apache.org/jira/browse/RANGER-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1428: - Summary: In certain scenario user data contains junk email-id (was: Access type for Knox under Audit tab is not displayed and In certain scenario user data contains junk email-id) > In certain scenario user data contains junk email-id > > > Key: RANGER-1428 > URL: https://issues.apache.org/jira/browse/RANGER-1428 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1428.patch > > > Description: > 1. Access type for knox is not displayed under Audit tab > 2. Junk email id is displayed in some scenario > Steps to reproduce point 2 > When added non-existing user while creating a service, it gets created in > user listing without email id but when same user is deleted it shows some > random data in email field in “User Profile deleted” entry > Steps to follow: > 1. Create a service with non-existing user(user will get created in user > listing) > 2. Now delete that user > 3. Go to Audit-Admin tab and check log for "User Profile deleted", in > email-id field it will show some random data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1428) Access type for Knox under Audit tab is not displayed and In certain scenario user data contains junk email-id
[ https://issues.apache.org/jira/browse/RANGER-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1428: - Summary: Access type for Knox under Audit tab is not displayed and In certain scenario user data contains junk email-id (was: Access type for Knox under Audit tab is not displayed and In certain scenario user data contains junk email-id if email-id is not specified) > Access type for Knox under Audit tab is not displayed and In certain scenario > user data contains junk email-id > -- > > Key: RANGER-1428 > URL: https://issues.apache.org/jira/browse/RANGER-1428 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > > Description: > 1. Access type for knox is not displayed under Audit tab > 2. Junk email id is displayed in some scenario > Steps to reproduce point 2 > When added non-existing user while creating a service, it gets created in > user listing without email id but when same user is deleted it shows some > random data in email field in “User Profile deleted” entry > Steps to follow: > 1. Create a service with non-existing user(user will get created in user > listing) > 2. Now delete that user > 3. Go to Audit-Admin tab and check log for "User Profile deleted", in > email-id field it will show some random data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1428) Access type for Knox under Audit tab is not displayed and In certain scenario user data contains junk email-id if email-id is not specified
Ankita Sinha created RANGER-1428: Summary: Access type for Knox under Audit tab is not displayed and In certain scenario user data contains junk email-id if email-id is not specified Key: RANGER-1428 URL: https://issues.apache.org/jira/browse/RANGER-1428 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.0 Reporter: Ankita Sinha Assignee: Ankita Sinha Fix For: 0.7.1 Description: 1. Access type for knox is not displayed under Audit tab 2. Junk email id is displayed in some scenario Steps to reproduce point 2 When added non-existing user while creating a service, it gets created in user listing without email id but when same user is deleted it shows some random data in email field in “User Profile deleted” entry Steps to follow: 1. Create a service with non-existing user(user will get created in user listing) 2. Now delete that user 3. Go to Audit-Admin tab and check log for "User Profile deleted", in email-id field it will show some random data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1379) Good coding practice for concurrent modification
[ https://issues.apache.org/jira/browse/RANGER-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865753#comment-15865753 ] Ankita Sinha commented on RANGER-1379: -- Patch committed. master : https://github.com/apache/ranger/commit/2d406044fafb574400bc66d06ee679f6dda5ed23 > Good coding practice for concurrent modification > > > Key: RANGER-1379 > URL: https://issues.apache.org/jira/browse/RANGER-1379 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.0 > > Attachments: RANGER-1379.patch > > > Good coding practice for checking is request from browser or console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1352) few cases where even if JSON is invalid then also message appears IMPORTED SUCCSSFULLY
[ https://issues.apache.org/jira/browse/RANGER-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1352: - Attachment: RANGER-1352.patch > few cases where even if JSON is invalid then also message appears IMPORTED > SUCCSSFULLY > -- > > Key: RANGER-1352 > URL: https://issues.apache.org/jira/browse/RANGER-1352 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Deepak Sharma >Assignee: Ankita Sinha > Fix For: 0.7.0 > > Attachments: RANGER-1352.patch > > > few cases where even if JSON is invalid then also message appears IMPORTED > SUCCSSFULLY. > case 1: > Json is correct but there is small mistake of case sensitivity instead true > its True. so ideally this json is considered as invalid from jsonlint. > but Ranger import pass in this case, but it does not import any policy. > Case 2: > if json file is empty , then also it says import successful, ideally it > should failed saying invalid json or something appropriate. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1352) few cases where even if JSON is invalid then also message appears IMPORTED SUCCSSFULLY
[ https://issues.apache.org/jira/browse/RANGER-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1352: - Attachment: RANGER-1352.patch > few cases where even if JSON is invalid then also message appears IMPORTED > SUCCSSFULLY > -- > > Key: RANGER-1352 > URL: https://issues.apache.org/jira/browse/RANGER-1352 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Deepak Sharma >Assignee: Ankita Sinha > Fix For: 0.7.0 > > Attachments: RANGER-1352.patch > > > few cases where even if JSON is invalid then also message appears IMPORTED > SUCCSSFULLY. > case 1: > Json is correct but there is small mistake of case sensitivity instead true > its True. so ideally this json is considered as invalid from jsonlint. > but Ranger import pass in this case, but it does not import any policy. > Case 2: > if json file is empty , then also it says import successful, ideally it > should failed saying invalid json or something appropriate. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RANGER-1352) few cases where even if JSON is invalid then also message appears IMPORTED SUCCSSFULLY
[ https://issues.apache.org/jira/browse/RANGER-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha reassigned RANGER-1352: Assignee: Ankita Sinha > few cases where even if JSON is invalid then also message appears IMPORTED > SUCCSSFULLY > -- > > Key: RANGER-1352 > URL: https://issues.apache.org/jira/browse/RANGER-1352 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Deepak Sharma >Assignee: Ankita Sinha > Fix For: 0.7.0 > > > few cases where even if JSON is invalid then also message appears IMPORTED > SUCCSSFULLY. > case 1: > Json is correct but there is small mistake of case sensitivity instead true > its True. so ideally this json is considered as invalid from jsonlint. > but Ranger import pass in this case, but it does not import any policy. > Case 2: > if json file is empty , then also it says import successful, ideally it > should failed saying invalid json or something appropriate. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
