[jira] Resolved: (JS2-1128) Spring LDAP DefaultDirContextValidator bug LDAP-189 causing unexpected error when borrowing new ContextSource from pool

["Ate Douma (JIRA)" <je...@portals.apache.org>]

     [ https://issues.apache.org/jira/browse/JS2-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ate Douma resolved JS2-1128.
----------------------------

    Resolution: Fixed

> Spring LDAP DefaultDirContextValidator bug LDAP-189 causing unexpected error when borrowing new ContextSource from pool
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JS2-1128
>                 URL: https://issues.apache.org/jira/browse/JS2-1128
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: LDAP
>    Affects Versions: 2.2.1
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 2.2.1
>
>
> I encountered unexpected errors during LDAP testing with the Spring LDAP PoolingContextSource failing to borrow new DirContexts.
> This turned out, after long, long, debugging to be caused by a bug in the DefaultDirContextValidator which "forgets" to set the right SearchControls scope (OBJECT_SCOPE) thereby falling back to the default ONELEVEL_SCOPE.
> Looking through Spring LDAP JIRA issue, this one turned out to be reported already but still not yet fixed: http://jira.springframework.org/browse/LDAP-189
> A workaround is easy to provide by setting a properly configured SearchControls object ourselves in the Spring assembly, which I will commit as example and default configuration in our security-ldap.xml Spring assembly file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org