You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/11/20 12:46:00 UTC
[jira] [Commented] (SYNCOPE-1513) Allow to customize security
headers
[ https://issues.apache.org/jira/browse/SYNCOPE-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978390#comment-16978390 ]
ASF subversion and git services commented on SYNCOPE-1513:
----------------------------------------------------------
Commit bd37f3d2e64b3e1d609580aebe00b0bfb84f5dae in syncope's branch refs/heads/2_1_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=bd37f3d ]
[SYNCOPE-1513] Adding options to console.properties
> Allow to customize security headers
> -----------------------------------
>
> Key: SYNCOPE-1513
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1513
> Project: Syncope
> Issue Type: Improvement
> Components: console
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 2.1.6, 3.0.0
>
>
> At the moment the following security headers are statically set by {{SyncopeConsoleApplication}}:
> {code}
> response.setHeader("X-XSS-Protection", "1; mode=block");
> response.setHeader("X-Content-Type-Options", "nosniff");
> response.setHeader("X-Frame-Options", "sameorigin");
> {code}
> Improve this by changing the code above to read security headers from {{console.properties}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)