[
https://issues.apache.org/jira/browse/HDFS-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HDFS-13951:
----------------------------------
Resolution: Fixed
Fix Version/s: 3.3.0
Status: Resolved (was: Patch Available)
thanks, committed to trunk.
w.r.t token APIs, I've looked at the new dtfetcher code, and it is better, but
it isn't quite there yet. For the S3A DT work, in particular, I'd like to be
able to issue a DT if the FS has delegation enabled, irrespective of the
security settings, but the {{isTokenRequired()}} method on the interface
doesn't pass in the URI, so you can't tell if a token is needed or not.
The fetcher needs to handle the case of {{addDelegationTokens}} returning null
and treat that as a valid outcome meaning "we turned out not to have any after
all".
> HDFS DelegationTokenFetcher can't print non-HDFS tokens in a tokenfile
> ----------------------------------------------------------------------
>
> Key: HDFS-13951
> URL: https://issues.apache.org/jira/browse/HDFS-13951
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: tools
> Affects Versions: 3.2.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 3.3.0
>
> Attachments: HDFS-13951-001.patch
>
>
> the fetchdt command can fetch tokens for filesystems other than hdfs (s3a,
> abfs, etc), but it can't print them, as it assumes all tokens in the file are
> subclasses of
> {{org.apache.hadoop.hdfs.security.token.delegation.DelegationTokenIdentifier}}
> & uses this fact in its decoding. It deserializes the token byte array
> without checking kind and so ends up with invalid data.
> Fix: ask the tokens to decode themselves; only call toStableString() if an
> HDFS token.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
