You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Larry McCay (JIRA)" <ji...@apache.org> on 2016/01/06 21:10:39 UTC

[jira] [Commented] (HADOOP-12691) Add CSRF Filter to Hadoop Common

    [ https://issues.apache.org/jira/browse/HADOOP-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086200#comment-15086200 ] 

Larry McCay commented on HADOOP-12691:
--------------------------------------

I will write up a quick design document for this filter and attach.
I intend to add it to the org/apache/hadoop/security/http/ package along side CrossOriginFilter.java.

> Add CSRF Filter to Hadoop Common
> --------------------------------
>
>                 Key: HADOOP-12691
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12691
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>             Fix For: 3.0.0
>
>
> CSRF prevention for REST APIs can be provided through a common servlet filter. This filter would check for the existence of an expected (configurable) HTTP header - such as X-Requested-By.
> The fact that CSRF attacks are entirely browser based means that the above approach can ensure that requests are coming from either: applications served by the same origin as the REST API or that there is explicit policy configuration that allows the setting of a header on XmlHttpRequest from another origin.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)