Setting an "idle-time-limit" global configuration property has no effect.
- Setup a standalone instance with default configuration/ACIs
- Set a idle-time-limit in global configuration, for example 3 mins:
- BIND as a non-root client connection.Any anonymous connection from a client (Apache Directory Studio for example) will do.
- Leave the client connected and idle beyond the configured timeout of 3 mins.
Client should be disconnected and a message logged in the access logs, as in version 3.5.x:
Idle client connections are not disconnected beyond the configured time out.