[
https://issues.apache.org/jira/browse/SENTRY-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Chanan updated SENTRY-480:
----------------------------------
Attachment: SENTRY-480.patch
Here's another patch with the following main differences:
1) doesn't build a binding, only uses the file provider backend and the
validators. Thus, we don't require the binding which is tricky to get right
anyway (the binding really runs in the server...are we convinced we have all
the right system properties, etc to get it to work)?
2) because of 1), doesn't pass the policy file via the configuration file,
takes it on the command line. We need the configuration file to specify the
service info; having both the policy file and the service info in there means
users would have to create a configuration file just for use of the tool.
3) Adds some additional compatibility checking around the fact that role names
are lower cased in the service but at least the solr backend supported cased
role names.
> Create import tool that will load policy file about Solr into the DB store
> --------------------------------------------------------------------------
>
> Key: SENTRY-480
> URL: https://issues.apache.org/jira/browse/SENTRY-480
> Project: Sentry
> Issue Type: Improvement
> Reporter: guoquan
> Assignee: guoquan
> Attachments: SENTRY-480-basis-generic-model.patch,
> SENTRY-480.002.patch, SENTRY-480.003.patch, SENTRY-480.004.patch,
> SENTRY-480.commontool.patch, SENTRY-480.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
