You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ate Douma (JIRA)" <je...@portals.apache.org> on 2010/01/13 02:51:54 UTC
[jira] Resolved: (JS2-1096) Several issues with
LdapAuthenticationProvider and LdapContextProxy: rewrite using Spring LDAP
instead
[ https://issues.apache.org/jira/browse/JS2-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma resolved JS2-1096.
----------------------------
Resolution: Fixed
> Several issues with LdapAuthenticationProvider and LdapContextProxy: rewrite using Spring LDAP instead
> ------------------------------------------------------------------------------------------------------
>
> Key: JS2-1096
> URL: https://issues.apache.org/jira/browse/JS2-1096
> Project: Jetspeed 2
> Issue Type: Bug
> Components: LDAP
> Affects Versions: 2.2.0
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.2.1
>
>
> With the migration and rewrite of the LDAP security mapping from Jetspeed 2.1.3 to 2.2 several problems and issues were introduced.
> One specific area is the authentication and context proxying which more or less got broken under certain conditions and configurations.
> JS2-1030 already indicates one of these, but also the context proxying (auto-recreation of stale/broken context) no longer works properly.
> As with Jetspeed 2.2 we started using Spring LDAP which provides an LDAP context pooling solution, I've decided to largely rewrite the LdapAuthenticationProvider to leverage Spring LDAP and drop the LdapContextProxy.
> As result of this rewrite, AFAIK JS2-1030 now also should be fixed as side-effect.
--
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