[
https://issues.apache.org/jira/browse/CASSANDRA-11097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878618#comment-16878618
]
Alex Petrov commented on CASSANDRA-11097:
-----------------------------------------
[~andrew.tolbert] I should've mentioned heartbeats. In case there's a
connection that has no traffic at all, including heartbeats, it should be timed
out. "Alive and well" connections are ok. However, if there is any defunct
connection that wasn't properly closed, it can be dropped. If the technical
part of this ticket is solid, I'll make sure to add a doc/news entry to
highlight that its counterpart is a heartbeat.
> Idle session timeout for secure environments
> --------------------------------------------
>
> Key: CASSANDRA-11097
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11097
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/CQL
> Reporter: Jeff Jirsa
> Assignee: Alex Petrov
> Priority: Low
> Labels: lhf, ponies
>
> A thread on the user list pointed out that some use cases may prefer to have
> a database disconnect sessions after some idle timeout. An example would be
> an administrator who connected via ssh+cqlsh and then walked away.
> Disconnecting that user and forcing it to re-authenticate could protect
> against unauthorized access.
> It seems like it may be possible to do this using a netty
> {{IdleStateHandler}} in a way that's low risk and perhaps off by default.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
