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

ASF subversion and git services commented on ATLAS-5019:
--------------------------------------------------------

Commit 9a752f125617a71e0c85f68aab907b48a8fb3ac7 in atlas's branch 
refs/heads/atlas-2.5 from pareshd
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9a752f125 ]

ATLAS-5019: Add header in atlas login.jsp page (#335)

(cherry picked from commit 008f7548752dafa25a7f4ba336b89be2557e0926)


> Add header in atlas login.jsp page
> ----------------------------------
>
>                 Key: ATLAS-5019
>                 URL: https://issues.apache.org/jira/browse/ATLAS-5019
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Paresh Devalia
>            Assignee: Paresh Devalia
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Currently, Apache Atlas does not include essential HTTP security headers 
> login.jsp page. This can expose the application to common web vulnerabilities.
>  * {{X-Frame-Options,}} 
> {{{}X-Content-Type-Options,{}}}{{{}X-XSS-Protection,{}}} 
> {{Content-Security-Policy}}
>  * In addition to these defaults, support is also added to configure *custom 
> HTTP headers* via the {{properties}} file using the {{atlas.headers.*}} 
> prefix. This allows users to define additional response headers as needed 
> without changing the codebase or override the header.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to