[
https://issues.apache.org/jira/browse/KARAF-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013520#comment-18013520
]
ASF GitHub Bot commented on KARAF-7671:
---------------------------------------
mattrpav commented on PR #1945:
URL: https://github.com/apache/karaf/pull/1945#issuecomment-3181003565
@globalbus the cache needs to be cleared on any config change, data change
and connection status change. If the LDAP server changes (connect-disconnect),
it is not safe to presume the data will be the same.
I'm not married to the static class, but injecting anything into Karaf's
JAAS module system is complicated to get consistent via all the provisioning
methods: cfg file, blueprint deployment or scr deployment.
I'm leaning to keep this change to be "fix" what is broken and then discuss
a refactor/improvement as a follow-on activity.
> LDAP login module cache fixes
> -----------------------------
>
> Key: KARAF-7671
> URL: https://issues.apache.org/jira/browse/KARAF-7671
> Project: Karaf
> Issue Type: Task
> Affects Versions: 4.4.3
> Reporter: Matt Pavlovich
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 4.5.0, 4.4.9
>
>
> 1. Cache is cleared on every login via the initialize method
> 2. LDAPLoginModule needs thread synchronization fixes to not rely on
> method-sync and class-level static cache field.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
