[
https://issues.apache.org/jira/browse/KNOX-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242563#comment-14242563
]
Kevin Minder commented on KNOX-479:
-----------------------------------
Just to confirm, the purpose of adding the cacheManager was to prevent repeated
group lookup via LDAP correct? So shouldn't its use should be more coupled to
the use of Service Level Authorization and then only in cases where JSESSIONID
is properly used? I guess I'm trying to remember why you are coupling this to
HS2 access.
> Remove cacheManager configuration from template files
> -----------------------------------------------------
>
> Key: KNOX-479
> URL: https://issues.apache.org/jira/browse/KNOX-479
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Larry McCay
> Assignee: Larry McCay
> Fix For: 0.6.0
>
>
> The cacheManager configuration needs to be removed from the general purpose
> template files. We will create a new topology template to show how to use it
> for xDBC->knox->HS2 access - since this is where it is most needed. The
> specialized hivedriver topology will only have the hive routing service
> defined.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
