[
https://issues.apache.org/jira/browse/KNOX-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dilli Arumugam updated KNOX-136:
--------------------------------
Description:
There is no 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.
was:
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.
> 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 no 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
