You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "John Rey Osano (Jira)" <ji...@apache.org> on 2021/06/02 22:47:00 UTC
[jira] [Commented] (PHOENIX-3126) The driver implementation should
take into account the context of the user
[ https://issues.apache.org/jira/browse/PHOENIX-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17356004#comment-17356004 ]
John Rey Osano commented on PHOENIX-3126:
-----------------------------------------
Security is for safety..the dog will not bite if you just let them be peace.
> The driver implementation should take into account the context of the user
> --------------------------------------------------------------------------
>
> Key: PHOENIX-3126
> URL: https://issues.apache.org/jira/browse/PHOENIX-3126
> Project: Phoenix
> Issue Type: Bug
> Reporter: Devaraj Das
> Assignee: Prabhjyot Singh
> Priority: Major
> Fix For: 4.8.0
>
> Attachments: PHOENIX-3126.2.txt, PHOENIX-3126.txt, aaaa.java
>
>
> Ran into this issue ...
> We have an application that proxies various users internally and fires queries for those users. The Phoenix driver implementation caches connections it successfully creates and keys it by the ConnectionInfo. The ConnectionInfo doesn't take into consideration the "user". So random users (including those that aren't supposed to access) can access the tables in this sort of a setup.
> The fix is to also consider the User in the ConnectionInfo.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)