Adding Social Sign In via amplify auth update causes error HostedUIProvidersCustomResourceInputs (Custom::LambdaCallout) while amplify push #13239
Comments
|
Hey @iwishApp 👋 thanks for raising this! We've made a few enhancements and fixes around auth in later versions of the CLI. If you upgrade to the latest CLI (12.4.0 at the time of writing) do you still encounter this error? |
josefaidt
added
the
pending-response
|
Upgraded to 12.4.0. Error still there: Cloudwatch logs:
|
github-actions
bot
removed
the
pending-response
|
We use Email as login mechanism. Now we want to add Apple Sign In. If I add Social Sign In via Amplify Studio, I cannot choose Email from drop down list. However our logic doesn't require "email", we had "requiredAttributes": [], before adding Sign In with apple. |
|
Hey @iwishApp thanks for clarifying! How was this user pool originally configured (e.g. "default" config with email as login mechanism)? Do you recall which version of the CLI was used when creating it? |
josefaidt
added
the
pending-response
|
@josefaidt I was able to run into the issue when running the following For |
Probably it was CLI v. 9.2.0 or 9.2.1 at the moment of Auth deployment. backend-config.json "auth": {
"MyAppName": {
"customAuth": false,
"dependsOn": [],
"frontendAuthConfig": {
"mfaConfiguration": "OFF",
"mfaTypes": [
"SMS"
],
"passwordProtectionSettings": {
"passwordPolicyCharacters": [],
"passwordPolicyMinLength": 8
},
"signupAttributes": [],
"socialProviders": [],
"usernameAttributes": [
"EMAIL"
],
"verificationMechanisms": [
"EMAIL"
]
},
"providerPlugin": "awscloudformation",
"service": "Cognito"
}
}
cli-inputs.json
{
"version": "1",
"cognitoConfig": {
"identityPoolName": "testAuthIdentityPool",
"allowUnauthenticatedIdentities": true,
"resourceNameTruncated": "MyAppName045e50a",
"userPoolName": "MyAppName",
"autoVerifiedAttributes": [
"email"
],
"mfaConfiguration": "OFF",
"mfaTypes": [
"SMS Text Message"
],
"smsAuthenticationMessage": "Your authentication code is {####}",
"smsVerificationMessage": "Your verification code is {####}",
"emailVerificationSubject": "MyAppName verification code",
"emailVerificationMessage": "Your verification code is {####}",
"defaultPasswordPolicy": false,
"passwordPolicyMinLength": 8,
"passwordPolicyCharacters": [],
"requiredAttributes": [],
"aliasAttributes": [],
"userpoolClientGenerateSecret": false,
"userpoolClientRefreshTokenValidity": 30,
"userpoolClientWriteAttributes": [],
"userpoolClientReadAttributes": [],
"userpoolClientLambdaRole": "MyAppName5e50a_userpoolclient_lambda_role",
"userpoolClientSetAttributes": false,
"sharedId": "5e50a",
"resourceName": "MyAppName",
"authSelections": "identityPoolAndUserPool",
"serviceName": "Cognito",
"usernameAttributes": [
"email"
],
"useDefault": "manual",
"userPoolGroups": false,
"userPoolGroupList": [],
"adminQueries": false,
"thirdPartyAuth": false,
"authProviders": [],
"usernameCaseSensitive": false,
"useEnabledMfas": true,
"authRoleArn": {
"Fn::GetAtt": [
"AuthRole",
"Arn"
]
},
"unauthRoleArn": {
"Fn::GetAtt": [
"UnauthRole",
"Arn"
]
},
"breakCircularDependency": true,
"dependsOn": []
}
}I have non-stop spinning activity indicator in the Authentication section in AWS Amplify web portal: |
github-actions
bot
removed
the
pending-response
|
Hey @iwishApp would you mind posting the project ID output from |
josefaidt
added
the
pending-response
ID 4986c94d24ca7c5f303272240a6d0801 |
github-actions
bot
removed
the
pending-response
|
Hey @iwishApp was
Is this a production environment? There is a trigger to migrate users, however this migration will also entail updating any records stored in DynamoDB if you are currently using |
josefaidt
added
the
pending-response
|
Hey @iwishApp I wanted to follow-up on this issue and see if you're still experiencing this? |
|
Hello, I ended up by resetting dev environment. |
github-actions
bot
removed
the
pending-response
|
@iwishApp thank you for the confirmation. Closing this issue for now, please feel free in reaching out to us if you require any assistance. |
|
|
@josefaidt I still face this issue. Tried creating auth from scratch and just Signin with apple creates problem. Can't deploy from studio or cli. |
How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
11.0.5
What operating system are you using?
MacOS Ventura 13.4
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes.
Describe the bug
Expected behavior
I want to configure Sign in with Apple for project with existing Cognito email auth.
Reproduction steps
1 Updating auth via amplify update auth
• What do you want to do? Update OAuth social providers
• Select the identity providers you want to configure for your user pool: Sign in with Apple
• Enter your Services ID for your OAuth flow: com.myapp.myapp.sid
• Enter your Team ID for your OAuth flow: ****
• Enter your Key ID for your OAuth flow: ****
• Enter your Private Key for your OAuth flow: *****
Note: For the Private key I am entering key from .p8 file by removing -----BEGIN PRIVATE KEY-----, -----END PRIVATE KEY-----, \n, space at the end of line and pasting main private key in single line.
2 Applying change to cloud via amplify push Produced error mentioned above
Project Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: