falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-229) Enable SSL for Falcon REST API
Date Tue, 28 Jan 2014 04:11:38 GMT

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

Venkatesh Seetharam commented on FALCON-229:

Thanks [~sriksun]. My understanding is that this jira consumes FALCON-218 implying:

* This needs to be based on FALCON-17 enhancements
* Needs a way to send the authenticated user from Prism to Falcon - I'm sending user.name
as a query parameter, we may beed something secure
* Implement Prism as a trusted service by Falcon - BasicAuthFilter implements authentication
and *sync* path also has this filer applied which means Prism will authenticate Falcon

Sorry that FALCON-18 also has changed significantly and this patch needs to be rebased.

> Enable SSL for Falcon REST API
> ------------------------------
>                 Key: FALCON-229
>                 URL: https://issues.apache.org/jira/browse/FALCON-229
>             Project: Falcon
>          Issue Type: Sub-task
>    Affects Versions: 0.5
>            Reporter: Venkatesh Seetharam
>            Assignee: Srikanth Sundarrajan
>              Labels: security
>         Attachments: FALCON-229-v2.patch, FALCON-229.patch
> Good to have but not in the first iteration.

This message was sent by Atlassian JIRA

View raw message