You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/03/08 20:00:42 UTC

[jira] [Commented] (KNOX-679) Make ResponseCookieFilter Configurable

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

ASF subversion and git services commented on KNOX-679:
------------------------------------------------------

Commit a6d4cbab6e36341ed0bc5eccabe49d1277271d74 in knox's branch refs/heads/master from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=a6d4cba ]

KNOX-679 - Make ResponseCookieFilter Configurable

> Make ResponseCookieFilter Configurable
> --------------------------------------
>
>                 Key: KNOX-679
>                 URL: https://issues.apache.org/jira/browse/KNOX-679
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>             Fix For: 0.9.0
>
>
> There are times when certain cookies need to not be allowed to be set. For instance, when using a Knox application to facilitate a central login page, the inclusion of the JSESSIONID cookie when interacting with the KnoxSSO service with the Shiro provider interferes with forcing the user to relogin.
> This change will allow a topology to be crafted such that the login does not result in a JSESSIONID being set.



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