[
https://issues.apache.org/jira/browse/KNOX-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Zampino resolved KNOX-2210.
----------------------------------
Resolution: Fixed
> Gateway-level configuration for server-managed Knox token state
> ---------------------------------------------------------------
>
> Key: KNOX-2210
> URL: https://issues.apache.org/jira/browse/KNOX-2210
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.4.0
> Reporter: Philip Zampino
> Assignee: Philip Zampino
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, use of the token state service by Knox Token service deployments
> and JWT providers is configured independently. This is due to the fact that
> there can be multiple deployments of the Knox Token service (i.e., multiple
> topologies), and each can choose whether server-management of token state is
> desired.
> However, in the simplest deployment scenarios, there is a single topology
> providing the Knox Token service, and one or more topologies with providers
> that verify those tokens for authentication. In these cases, would be simpler
> to have a single gateway-level configuration property that enables/disables
> the use of the TokenStateService for all KnoxToken service deployments and
> JWT provider deployments.
> The KnoxToken service and the providers should check for a topology-level
> override (e.g., service param, provider param), which should be applied if
> present. In the absence of an topology-level override, the gateway-level
> configuration property should be referenced and applied.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
