falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-11) Add support for security in Falcon
Date Fri, 07 Feb 2014 00:58:24 GMT

    [ https://issues.apache.org/jira/browse/FALCON-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894057#comment-13894057

Arpit Gupta commented on FALCON-11:

bq. Can the blacklisted users be defaulted to maintain compatibility

I agree with [~svenkat] that having defaults is not helpful. Users can start the services
as any arbitrary users then these black listed users such as falcon, hdfs etc. If that is
the case then we dont to block calls for hdfs or falcon user. I like the idea of this feature
but i believe the default should be an empty list. The same issue exists with startup properties.
We dont know which users these services will be running as so blocking them by default does
not help.

> Add support for security in Falcon
> ----------------------------------
>                 Key: FALCON-11
>                 URL: https://issues.apache.org/jira/browse/FALCON-11
>             Project: Falcon
>          Issue Type: Improvement
>    Affects Versions: 0.3
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>              Labels: security
>         Attachments: FALCON-11.patch
>   Original Estimate: 336h
>  Remaining Estimate: 336h
> The following is the break up of tasks for Falcon to be secure and work with secure Hadoop.
> 1. Secure Falcon daemon - needs to login with keytabs
> 2. Secure Hadoop client interface - HDFS
> 3. Secure Oozie client interface
> 4. Secure Falcon Web Interface
> 5. Secure Falcon Client Interface
> ..etc.

This message was sent by Atlassian JIRA

View raw message