incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-3788) Perform E2E testing of Ambari with api.csrfPrevention.enabled=true
Date Mon, 18 Nov 2013 18:01:25 GMT

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

Yusaku Sako commented on AMBARI-3788:
-------------------------------------

Nice.  Thanks [~BuzhorDenys].

> Perform E2E testing of Ambari with api.csrfPrevention.enabled=true
> ------------------------------------------------------------------
>
>                 Key: AMBARI-3788
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3788
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.4.2
>            Reporter: Denys Buzhor
>            Assignee: Denys Buzhor
>             Fix For: 1.4.2
>
>         Attachments: results.txt
>
>
> Set *api.csrfPrevention.enabled=true* in *ambari.properties*, restart ambari server,
and verify that Ambari Web works properly with that option on.
> Before testing Ambari Web, make sure that the POST calls to the API does NOT work unless
you pass the *X-Requested-By* option (to make sure that the CSRF filter is in effect).



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message