[jira] [Created] (HADOOP-17383) AbstractS3ATokenIdentifier to provide issue date == created && max date == expiry time

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (HADOOP-17383) AbstractS3ATokenIdentifier to provide issue date == created && max date == expiry time

Steve Loughran (Jira)
Jungtaek Lim created HADOOP-17383:
-------------------------------------

             Summary: AbstractS3ATokenIdentifier to provide issue date == created && max date == expiry time
                 Key: HADOOP-17383
                 URL: https://issues.apache.org/jira/browse/HADOOP-17383
             Project: Hadoop Common
          Issue Type: Improvement
          Components: fs/s3
    Affects Versions: 3.3.0
            Reporter: Jungtaek Lim


As we've seen the behavior from HADOOP-17379, AbstractS3ATokenIdentifier doesn't guarantee providing correct "issue date" and "max date" before HADOOP-17379, and even after, "max date" is not a thing we can make a guarantee only with AbstractS3ATokenIdentifier, as there's no information.

In the meanwhile, I realized there're two methods in AbstractS3ATokenIdentifier, getCreated() and getExpiryTime(), which feel like the same purpose with getIssueDate() and getMaxDate() in AbstractDelegationTokenIdentifier.

If we think these pairs are doing the same, we can just override AbstractS3ATokenIdentifier.getIssueDate() to call getCreated() && AbstractS3ATokenIdentifier.getMaxDate() to call getExpiryTime().



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]