[ https://issues.apache.org/jira/browse/CASSANDRA-11097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Petrov updated CASSANDRA-11097: ------------------------------------ Source Control Link: https://github.com/apache/cassandra/commit/0240a4659d761f06f94f8cd97097f2d0ad2d220c Status: Resolved (was: Ready to Commit) Resolution: Fixed > 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 > Fix For: 4.0 > > > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org