[
https://issues.apache.org/jira/browse/HADOOP-16572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929169#comment-16929169
]
Steve Loughran commented on HADOOP-16572:
-----------------------------------------
Also - we should set maxdate if there is one, so diagnostics tools can examine
DTs and warn of final expiry info without having to know of s3a DTs. This may
be of use to renewers in general
> S3A DT support to warn when loading expired token
> -------------------------------------------------
>
> Key: HADOOP-16572
> URL: https://issues.apache.org/jira/browse/HADOOP-16572
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Environment: CLI with HADOOP_TOKEN_PATH pointing at a file from the
> day before, containing an assumed Role DT, which was being loaded ahead of
> any setting in the XML file
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> (This just cost me half an hour as somehow as working CLI command stopped
> working since the day before, and I've been playing with endpoints and
> signing before I realised it)
> _If the DT provider code loads a token from a file, it doesn't check or warn
> for an expired token -all you get is a 400 Bad request failure_
> This not at all obvious.
> Proposed
> * WARN if now > expiry
> * extra entry in troubleshooting for 400
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
