ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13278) Add security-related HTTP headers to keep Ambari up to date with best-practices
Date Thu, 01 Oct 2015 21:32:26 GMT

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

Hudson commented on AMBARI-13278:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.1 #626 (See [https://builds.apache.org/job/Ambari-branch-2.1/626/])
AMBARI-13278. Add security-related HTTP headers to keep Ambari up to (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b23f448d58ad3feed23d28e02cda2a3f351be0fc])
* ambari-server/src/test/java/org/apache/ambari/server/security/SecurityHeaderFilterTest.java
* ambari-server/conf/unix/ambari.properties
* ambari-server/src/main/java/org/apache/ambari/server/security/SecurityHeaderFilter.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* ambari-server/conf/windows/ambari.properties


> Add security-related HTTP headers to keep Ambari up to date with best-practices
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-13278
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13278
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>             Fix For: 2.2.0, 2.0.3, 2.1.3
>
>         Attachments: AMBARI-13278_branch-2.0.maint_01.patch, AMBARI-13278_branch-2.0.maint_02.patch,
AMBARI-13278_branch-2.1_01.patch, AMBARI-13278_trunk_01.patch
>
>
> Add security-related HTTP headers to keep Ambari up to date with best-practices. 
> * Strict-Transport-Security
> * X-Frame-Options
> * X-XSS-Protection
> These headers should be configurable via the ambari.properties such that they may be
turned on or off - and set to some custom value.
> The default value for this headers should be as follows:
> * Strict-Transport-Security: max-age=31536000
> * X-Frame-Options: DENY
> * X-XSS-Protection: 1; mode=block
> Strict-Transport-Security should only be turned on if SSL is enabled.
> The relevant Ambari properties should be:
> * Strict-Transport-Security: http.strict-transport-security
> * X-Frame-Options: http.x-frame-options
> * X-XSS-Protection: http.x-xss-protection
> By setting any of these to be empty, the header is to be turned off (or not set).
> For example:
> {code:title=Sets Strict-Transport-Security to a custom value}
> http.strict-transport-security=max-age=31536000; includeSubDomains
> {code}
> {code:title=Turns Strict-Transport-Security off}
> http.strict-transport-security=
> {code}



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

Mime
View raw message