[
https://issues.apache.org/jira/browse/KNOX-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773315#comment-13773315
]
Kevin Minder edited comment on KNOX-136 at 9/20/13 7:07 PM:
------------------------------------------------------------
Please provide an example of how this would be specified in the topology files
and the resulting web.xml content. Also you will need to give some through as
to what "provider" would be responsible for taking care of this processing.
was (Author: kminder):
Please provide an example of how this would be specified in the topology
files and the resulting web.xml content.
> Knox should support configurable session timeout
> ------------------------------------------------
>
> Key: KNOX-136
> URL: https://issues.apache.org/jira/browse/KNOX-136
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.3.0
> Reporter: Dilli Arumugam
> Assignee: Dilli Arumugam
> Fix For: 0.3.0
>
>
> There is not clue what is the session timeout in Knox.
> When a user authenticates to Knox, a session is created in Knox and a
> JSESSIONID cookie is returned to the client.
> But, there is no clue how long this session is valid.
> We should allow customers to set different session timeouts.
> At the minimum, we should add
> <session-config>
> <!-- web.xml expects the session timeout in minutes: -->
> <session-timeout>30</session-timeout>
> </session-config>
> in the web.xml created by deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
