[
https://issues.apache.org/jira/browse/KNOX-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657678#comment-15657678
]
Larry McCay commented on KNOX-571:
----------------------------------
I see - so you are talking about an approach that a Knox specific integration
be done for every UI.
This could potentially be done over time but I think that many UIs across the
various projects will have a hard time justifying this integration for Knox.
Let's start a KIP for this and try and address the different categories of
applications that I described above.
Maybe we can identify different phases of delivery where it can be iterated
over time and still at least have an understanding of what the behavior should
be.
> UI Web pages should have a way to logout
> ----------------------------------------
>
> Key: KNOX-571
> URL: https://issues.apache.org/jira/browse/KNOX-571
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.7.0
> Environment: Redhat/Windows
> Reporter: Jeffrey E Rodriguez
> Fix For: Future
>
> Attachments: knox_logout_design.jpg
>
>
> UI using Knox as a proxy should have a way to define a logout so Browser to
> Knox session is invalidated and user is challenged for Authentication. This
> is a web security requirement to prevent session hijacking attacks.
> References
> https://www.owasp.org/index.php/Session_hijacking_attack
> https://owasp.org/index.php/Testing_for_logout_functionality_%28OTG-SESS-007%29
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
