[KNOX-458] Surface Config for Shiro LDAP Connection Pooling

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Server
• Assignee: Larry McCay
• Reporter: Larry McCay
• Created: 29/Oct/14 16:47
• Updated: 07/Nov/18 20:19

Description

The default connection pooling in Shiro provides pooling for system-users but not end users. The assumption being that the JSESSIONID cookie and session state can optimize away the hits to the LDAP server.

This assumption isn't sufficient for all possible REST clients and some deployments may know that they need additional connection pooling.

Shiro does not appear to provide standard shiro.ini configuration for this and we likely need to programmatically surface a configuration item for this provider in order to set it properly within our realm implementation.

Usecase described by acoliver.