Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Applications/users could connect to gaianDB using their own authentication information - for example userid/password in the simple case. Here the ranger plugin will use that id for policy checks.
However in a multi tiered architecture a service id (aka non personal account) may be used, and somehow the user to be impersonated is passed via an additional property. This has a number of implications to the system configuration, derby/gaiandb configuration & the plugin implementation.
Opening this Jira as a placeholder and will add a document soon (++days) on the same to capture some of the discussion around this area in recent days.