You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Larry McCay (JIRA)" <ji...@apache.org> on 2016/08/05 16:10:20 UTC
[jira] [Updated] (KNOX-458) Surface Config for Shiro LDAP
Connection Pooling
[ https://issues.apache.org/jira/browse/KNOX-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Larry McCay updated KNOX-458:
-----------------------------
Fix Version/s: (was: Future)
0.10.0
> Surface Config for Shiro LDAP Connection Pooling
> ------------------------------------------------
>
> Key: KNOX-458
> URL: https://issues.apache.org/jira/browse/KNOX-458
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Larry McCay
> Assignee: Larry McCay
> Fix For: 0.10.0
>
>
> 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].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)