[
https://issues.apache.org/jira/browse/HDDS-17654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136340#comment-18136340
]
Fabian Morgan commented on HDDS-17654:
--------------------------------------
hi [~adoroszlai] - this was already discussed with [~Sammi] and is one reason
why the sts tests were separated out. We need the test coverage for expired
tokens. Previously, there were many latent issues that caused the expired
token message not to bubble up to the client and having the acceptance test
ensures someone in the future doesn't reintroduce.
> Avoid or reduce wait for "expired" token
> ----------------------------------------
>
> Key: HDDS-17654
> URL: https://issues.apache.org/jira/browse/HDDS-17654
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: test
> Reporter: Attila Doroszlai
> Assignee: Fabian Morgan
> Priority: Major
>
> STS acceptance test verifies expiration using a token with 15 minutes
> duration, the minimum allowed. When it reaches the "Expired Token" test
> case, it waits until any remaining lifetime is elapsed.
> GitHub runners are shared resources, the test should not sleep for minutes.
> Minimum token duration is validated by both Ozone STS and AWS CLI. We can
> tweak Ozone to allow a custom short duration for tests, but need to find a
> way to make the request without client-side validation.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
