[
https://issues.apache.org/jira/browse/RANGER-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157125#comment-16157125
]
Nigel Jones commented on RANGER-1488:
-------------------------------------
Originally it was planned that authorization would be based purely on the user
that connects to gaianDB (which can support local users, or LDAP - the latter
being more likely in an enterprise) ie this user would be used within the
ranger/gaiandb plugin to determine access priviliges.
However feedback this week has suggested that *in addition*, it should be
possible to pass the userid as a connection parameter (derby supports this),
since it will be a 'non personal' or 'generic' server user id that may be
connecting to gaiandb in some use cases.
> Create Ranger plugin for gaiandb
> --------------------------------
>
> Key: RANGER-1488
> URL: https://issues.apache.org/jira/browse/RANGER-1488
> Project: Ranger
> Issue Type: New Feature
> Components: plugins
> Reporter: Nigel Jones
> Assignee: Nigel Jones
> Labels: VirtualDataConnector
>
> GaianDB is a distributed, federated database built on Apache Derby.
> The documentation is at
> https://github.com/gaiandb/gaiandb/blob/master/README.md - navigate up for
> the source.
> As part of a Virtual Connector Project based on Atlas we are using gaianDB to
> provide a virtualization layer. We need to control access to underlying
> resources and will be building a Ranger plugin for gaiandb to support this.
> GaianDB already has support for a form of policy plugin which allows the SQL
> to be intercepted.
> It is unclear if this code will sit
> - external to ranger/atlas ie in the gaianDB sources
> - as a sample in the Atlas project (so that we collate what is needed for
> the virtual connector project)
> - as a sample, or component in the Ranger project
> However it seems helpful to describe the proposal here and get
> feedback/dialogue in the ranger community :-)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
