-
Notifications
You must be signed in to change notification settings - Fork 824
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
For Auth, add PreventUserExistenceErrors parameter and update NodeJS runtime version #3534
Conversation
…rs: ENABLED. To use the latest AWS Lambda runtime, updated the runtime to nodejs12.x
@@ -367,7 +369,7 @@ Resources: | |||
- ' }' | |||
- '};' | |||
Handler: index.handler | |||
Runtime: nodejs10.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you try pushing this template and testing it?
I believe Cloudformation doesn't support in-line lambda's with Node 12.x runtime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CloudFormation does support Lambda Node 12.x runtime. Here is the documentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is for the Lambda functions - not for the in-line custom resources which you define in your cloudformation file. Have you tried pushing this template successfully?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codecov Report
@@ Coverage Diff @@
## master #3534 +/- ##
========================================
Coverage 58.18% 58.18%
========================================
Files 407 407
Lines 18758 18758
Branches 3750 3555 -195
========================================
Hits 10914 10914
- Misses 7162 7182 +20
+ Partials 682 662 -20
Continue to review full report at Codecov.
|
@beomseoklee Had to revert this due to an odd error happening in one of our tests. We'll figure out what's going on with the test and merge this again. This is the failed test: https://app.circleci.com/pipelines/github/aws-amplify/amplify-cli/2542/workflows/bbbb0bed-b0a4-4a0d-96c1-8cb6ba2f3739/jobs/36430 We need to change the expected error message here to "Incorrect username or password" but when I tried to update the test to that, for some reason the error we're getting is "Only radix 2, 4, 8, 16, 32 are supported" likely related to this issue just need to dig into why it's happening |
…enceErrors: ENABLED. (aws-amplify#3534)" (aws-amplify#5736) This reverts commit 5d474d3.
This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Issue: #4214
Description of changes:
According to the Amazon Cognito documentation, if
PreventUserExistenceErrors
parameter is enabled automatically after February 15th 2020, but it's somehow not through the AWS CloudFormation template.For the security best practice, this option needs to be enabled, so I've added
PreventUserExistenceErrors
parameter.In addition to the parameter, I've updated NodeJS runtime to the latest version for AWS Lambda functions.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.