You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/03/15 01:27:00 UTC
[jira] [Work logged] (KNOX-2551) Token state management
improvements
[ https://issues.apache.org/jira/browse/KNOX-2551?focusedWorklogId=565994&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-565994 ]
ASF GitHub Bot logged work on KNOX-2551:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Mar/21 01:26
Start Date: 15/Mar/21 01:26
Worklog Time Spent: 10m
Work Description: smolnar82 merged pull request #414:
URL: https://github.com/apache/knox/pull/414
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 565994)
Time Spent: 20m (was: 10m)
> Token state management improvements
> -----------------------------------
>
> Key: KNOX-2551
> URL: https://issues.apache.org/jira/browse/KNOX-2551
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 1.5.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Critical
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In this Jira a bunch of token management improvements is added:
> * AliasBasedTokenStateService is the default token state service implementation
> * Fixing parameter index in various token related log messages
> * Knox Token related aliases are stored under {{/knox/security/topology/__gateway/tokens}}
> * Addressing the side effects of optimistic replication in Knox HA mode using the ZK token state service
> * Avoid removing --max aliases from the unpersisted in-memory collection
> * ZK token state service performance improvements
> ** ZK token state service should configure ZKRemoteAliasService to not use local keystore
> ** ZK token state service should implement {{loadTokensFromPersistenceStore}} to avoid keystore lookup from the parent; it actually should do nothing as ZK entry change listeners populate in-memory collections in DefaultTokenStateService
> ** token eviction should run independently of {{loadTokensFromPersistenceStore}} (not like in AliasBasedTokenStateService as we no longer need to consider the global keystore locking in {{DefaultKeystoreService}})
> * Fixing {{addAlias}} in {{ZKRemoteAliasService}} to support saving updated data for already existing aliases
> * The token persister thread should be monitored and re-initiated n case an error occurrs during task execution
--
This message was sent by Atlassian Jira
(v8.3.4#803005)