Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use explicit tokenValidityUnits 'days' for userPoolClient refreshToken #10706

Conversation

joekiller
Copy link
Contributor

@joekiller joekiller commented Jul 7, 2022

Fixes RefreshToken sometimes not using correct units if it had been manually modified in the past ie aws-cloudformation/cloudformation-coverage-roadmap#606 (comment)

Description of changes

use explicit tokenValidityUnits 'days' for userPoolClient refreshToken otherwise units may not match what the CLI implies.

Issue #, if available

N/A

Description of how you validated changes

Added tests and validated CFN.

Checklist

  • [X ] PR description included
  • yarn test passes
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)
  • New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@joekiller joekiller requested a review from a team as a code owner July 7, 2022 00:50
@joekiller joekiller force-pushed the category-auth/use-explicit-token-validity-units branch 2 times, most recently from 0cd9f1f to 468760c Compare July 7, 2022 01:19
Fixes RefreshToken sometimes not using correct units if it had been manually modified in the past ie aws-cloudformation/cloudformation-coverage-roadmap#606 (comment)
@joekiller joekiller force-pushed the category-auth/use-explicit-token-validity-units branch from 468760c to 29c621f Compare July 7, 2022 01:22
@siegerts siegerts added the first-time-contributor The contribution is the first for this user in the repo label Jul 7, 2022
@joekiller
Copy link
Contributor Author

Seems unclear to me why the run-pr-e2e failed. Is there something I need to update?

Copy link
Contributor

@edwardfoyle edwardfoyle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. thanks for the contribution! I should be able to get the e2e tests to run

@edwardfoyle edwardfoyle self-assigned this Jul 21, 2022
Copy link
Contributor

@danielleadams danielleadams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is good to go - that failure was when a change that broke tests went into dev. At this point a rebase will require another e2e run, when all the other tests have passed.

@danielleadams danielleadams merged commit c9545be into aws-amplify:dev Jul 25, 2022
sundersc pushed a commit to sundersc/amplify-cli that referenced this pull request Jul 26, 2022
aws-amplify#10706)

Fixes RefreshToken sometimes not using correct units if it had been manually modified in the past ie aws-cloudformation/cloudformation-coverage-roadmap#606 (comment)
@joekiller joekiller deleted the category-auth/use-explicit-token-validity-units branch September 2, 2022 01:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
first-time-contributor The contribution is the first for this user in the repo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants