You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Hector Sandoval Chaverri (Jira)" <ji...@apache.org> on 2022/05/27 16:09:00 UTC

[jira] [Updated] (HADOOP-18264) ZKDelegationTokenSecretManager should handle duplicate Token sequenceNums

     [ https://issues.apache.org/jira/browse/HADOOP-18264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hector Sandoval Chaverri updated HADOOP-18264:
----------------------------------------------
    Priority: Minor  (was: Major)

> ZKDelegationTokenSecretManager should handle duplicate Token sequenceNums
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-18264
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18264
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Hector Sandoval Chaverri
>            Priority: Minor
>
> The ZKDelegationTokenSecretManager relies on the TokenIdentifier sequenceNumber to identify each Token in the ZK Store. It's possible for multiple TokenIdentifiers to share the same sequenceNumber, as this is an int that can overflow. 
> The AbstractDelegationTokenSecretManager uses a Map<TokenIdent, DelegationTokenInformation> so all properties in the TokenIdentifier must match. ZKDelegationTokenSecretManager should follow the same logic.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org