[
https://issues.apache.org/jira/browse/FC-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18001351#comment-18001351
]
Shawn McKinney commented on FC-327:
-----------------------------------
Why do we need to cache at all? One could make the argument that the directory
should be fast enough. For administrative operations that's an acceptable
tradeoff (slower performance) for up to date values. But what about
createSession? This happens a lot and for evaluating dynamic separation of duty
constraints during role activations there would be quite a hit reading all of
the roles and constraints stored. This would have to be done on every login.
For impls that don't use DSD an option should be available to turn off all
caching. This option will be included here.
> Upgrade from ehcache v2
> -----------------------
>
> Key: FC-327
> URL: https://issues.apache.org/jira/browse/FC-327
> Project: FORTRESS
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Shawn McKinney
> Priority: Major
> Fix For: 4.0.0
>
>
> Fortress core uses ehcache v2. It is getting long in tooth, has a number of
> CVE's, and needs to be replaced. Here we'll look at alternatives.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
