[
https://issues.jboss.org/browse/WFLY-2148?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on WFLY-2148:
----------------------------------------
Let me look at this after WFLY-1523, I would actually take this one step further to cover
cases where the console makes a lot of requests or scripted clients send in a lot of
non-batched requests.
It is possible for a users group membership to be changed between requests but it is
actually rare that we would expect that to happen so it may be better to cache using the
user and their groups as a key, a change in group membership would lead to a different key
and any operations to modify role mappings should clear the cache.
Cache role mapping results for the span of the overall operation
----------------------------------------------------------------
Key: WFLY-2148
URL:
https://issues.jboss.org/browse/WFLY-2148
Project: WildFly
Issue Type: Sub-task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Darran Lofthouse
Fix For: 8.0.0.CR1
Look into caching role mapping results for the duration of an overall operation. This
would be an impl detail of the RoleMapper. With our standard mappers, the mapping results
should not be changing in the middle of an operation, so I believe they should be
cacheable.
Likely place to cache them is as an attachment in a context object that will be passed in
to the Authorizer. It would have to be passed in to the RoleMapper as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira