[FALCON-11] Add support for security in Falcon

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.4, 0.3
• Fix Version/s: 0.5
• Labels: incompatible security
• Assignee: Venkatesh Seetharam
• Reporter: Venkatesh Seetharam
• Due: 24/May/13
• Created: 13/May/13 10:49
• Updated: 01/May/14 18:23
• Resolved: 01/May/14 18:23

Description

This jira only addresses authentication. 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.

Issue Links

• blocks: FALCON-222 Capturing Oozie logs post workflow completion needs to move into Falcon daemon
• blocks: FALCON-230 Add broker authentication support
• blocks: FALCON-274 Add broker ssl transport connector support
• blocks: FALCON-280 Validate the ACL in Feed entity with the user submitting the entity
• blocks: FALCON-242 Post processing is not called in Retention workflows
• breaks: FALCON-314 Fix integration test failure post FALCON-11
• is duplicated by: FALCON-149 Print FileSystem exception for debugging purposes
• links to: Patch Review

Sub-Tasks

• secure falcon daemon: Resolved
• Secure Hadoop client interface: Resolved
• Secure Oozie client interface: Resolved
• Secure Falcon Web Interface: Resolved
• Secure Falcon Client Interface: Resolved
• Secure the interface between Prism and Falcon Server in Distributed mode of execution: Resolved
• Secure hive/hcatalog client interface: Resolved
• Post processing should propagate user information in messages for offline processing: Resolved
• Secure Dashboard - need to send a valid user instead of 'admin': Resolved
• Enable SSL for Falcon REST API: Resolved
• Document security configuration: Resolved