You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Hongxu Ma (JIRA)" <ji...@apache.org> on 2017/06/30 03:09:00 UTC
[jira] [Assigned] (HAWQ-1493) Integrate Ranger lookup JAAS
configuration in ranger-admin plugin jar
[ https://issues.apache.org/jira/browse/HAWQ-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hongxu Ma reassigned HAWQ-1493:
-------------------------------
Assignee: Hongxu Ma (was: Radar Lei)
> Integrate Ranger lookup JAAS configuration in ranger-admin plugin jar
> ---------------------------------------------------------------------
>
> Key: HAWQ-1493
> URL: https://issues.apache.org/jira/browse/HAWQ-1493
> Project: Apache HAWQ
> Issue Type: Sub-task
> Components: Security
> Reporter: Hongxu Ma
> Assignee: Hongxu Ma
> Fix For: 2.3.0.0-incubating
>
>
> For support ranger lookup a kerberized HAWQ, we modify java.security file and add a .java.login.config file into ranger account now.
> But both of the two files are global, have influenced other program, so we need integrate the JAAS configuration in a private scope.
> After investigation, `setProperty("java.security.auth.login.config")` in ranger-admin plugin code is a good solution.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)