Closed mkaya95 closed 2 years ago
josefaidt
commented
2 years ago Hey @mkaya95 :wave: thanks for raising this! As we begin to look at reproducing this issue would you mind sharing your Auth resource's configuration by posting the contents of amplify/backend/auth/<resource-name>/cli-inputs.json (omitting any sensitive details)?
mkaya95
commented
2 years ago Hi @josefaidt 👋 Thank you for your response. Here is the my cli-inputs.json
{
"version": "1",
"cognitoConfig": {
"identityPoolName": "fxa_identitypool_864x01cb",
"allowUnauthenticatedIdentities": false,
"resourceNameTruncated": "fxa0300b5X1",
"userPoolName": "fxa",
"autoVerifiedAttributes": [
"email"
],
"mfaConfiguration": "OPTIONAL",
"mfaTypes": [
"SMS Text Message"
],
"smsAuthenticationMessage": "Your authentication code is {####}",
"smsVerificationMessage": "Your verification code is {####}",
"emailVerificationSubject": "Your verification code",
"emailVerificationMessage": "Your verification code is {####}",
"defaultPasswordPolicy": false,
"passwordPolicyMinLength": 8,
"passwordPolicyCharacters": [],
"requiredAttributes": [],
"aliasAttributes": [
"preferred_username"
],
"userpoolClientGenerateSecret": false,
"userpoolClientRefreshTokenValidity": 30,
"userpoolClientWriteAttributes": [
"email"
],
"userpoolClientReadAttributes": [
"email"
],
"userpoolClientLambdaRole": "fxa0300b5X1_userpoolclient_lambda_role",
"userpoolClientSetAttributes": false,
"authSelections": "identityPoolAndUserPool",
"resourceName": "fxa",
"serviceName": "Cognito",
"useDefault": "defaultSocial",
"sharedId": "0300b5X1",
"userPoolGroupList": [],
"userPoolGroups": false,
"usernameCaseSensitive": false,
"adminQueries": false,
"hostedUI": true,
"hostedUIDomainName": "fxaplayground",
"hostedUIProviderMeta": "[]",
"authProvidersUserPool": [],
"triggers": {},
"authRoleArn": {
"Fn::GetAtt": [
"AuthRole",
"Arn"
]
},
"unauthRoleArn": {
"Fn::GetAtt": [
"UnauthRole",
"Arn"
]
},
"breakCircularDependency": true,
"useEnabledMfas": false,
"dependsOn": [],
"oAuthMetadata": "{\"AllowedOAuthFlows\":[\"code\"],\"AllowedOAuthScopes\":[\"phone\",\"email\",\"openid\",\"profile\",\"aws.cognito.signin.user.admin\"],\"CallbackURLs\":[\"http://localhost:4200/dashboard/\",\"https://dev.xxxx.com/dashboard/\"],\"LogoutURLs\":[\"http://localhost:4200/\",\"https://dev.xxxx.com/\"]}",
"authProviders": [],
"parentStack": {
"Ref": "AWS::StackId"
},
"permissions": []
}
}Hey @mkaya95 thank you for posting that! Are you also able to clarify what version of the CLI was used prior to migrating, or what version of the CLI was used to initially create the auth resource?
mkaya95
commented
2 years ago Hey @mkaya95 thank you for posting that! Are you also able to clarify what version of the CLI was used prior to migrating, or what version of the CLI was used to initially create the auth resource?
Hi @josefaidt, I am not sure what version of CLI was used for creating. It can be 7.3.6, However, migrate attempting CLI version is 8.2.0
josefaidt
commented
2 years ago Hey @mkaya95 thank you for clarifying! I was not able to immediately reproduce this by creating an auth resource with an older CLI version (5.4.0) and migrating to the latest version of the CLI (8.3.0). Are you able to capture the diff of this property?
"usernameCaseSensitive": false,In the auth resource's built CloudFormation template we can see this is the only property used with UsernameConfiguration
"UsernameConfiguration": {
"CaseSensitive": false
},Hey @josefaidt, Thank you for your response.
fino-cloudformation-template.yml
usernameCaseSensitive:
Type: Stringparameters.json
"usernameCaseSensitive": false,After amplify auth update;
cli-inputs.json
"usernameCaseSensitive": false,build folder; build/fino-cloudformation-template.yml
"usernameCaseSensitive": {
"Type": "String"
},
...
...
...
"UsernameConfiguration": {
"CaseSensitive": false
},build/parameters.json
"usernameCaseSensitive": false,Hey @mkaya95 thank you for clarifying! Are you seeing a username configuration in the Cognito Console that's different than what you have locally? Are the values different in the #current-cloud-backend.zip archive (found in your s3 deployment bucket)?
josefaidt
commented
2 years ago Hey @mkaya95 :wave: just wanted to follow-up here and see if you are still experiencing this issue?
Chiida
commented
2 years ago Hi @josefaidt, as I know, @mkaya95 solved this issue and he'll post the solution here soon.
josefaidt
commented
2 years ago Hey @Chiida thanks for chiming in here! And glad to hear y'all were able to sort this out! I'll close this for now but I am looking forward to hearing about the solution @mkaya95 found
mkaya95
commented
2 years ago Hi @josefaidt,
Sorry for the late response. Deployment is passed successfully once I removed usernameCaseSensitive parameter from my configuration.
Thank you for your attention.
Before opening, please confirm:
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.18.2
Amplify CLI Version
8.2.0
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Amplify Categories
auth, function, api, notifications
Amplify Commands
push
Describe the bug
I would like to create pre-token generation trigger on my cognito. When I ran
amplify auth updatecommand it tells me that I need to migrate auth in order to continue. Then I migrated using default configuration. However I am receiving error when I am trying to push it.Expected behavior
Since I am not touching any configuration it should be successfully push.
Reproduction steps
Then I am receiving error that I shared on the Log output section.
GraphQL schema(s)
Log output
Additional information
When I researched this error on the internet I already found this issue however I have still problem even they said thats fixed in #9339