I'm trying to get Amplify + Cognito + Federated Office 365 / Azure AD login working. Currently stuck with "Invalid login token. Issuer doesn't match providerName". Somehow the JWT ends up with an iss: "https://cognito-idp.us-east-1.amazonaws.com/XYZ" which I suppose shouldn't be prepended with https.// ?
Would be super happy for any help
Figured it out. First param to await Auth.federatedSignIn is not the name of the federated identity provider in the Cognito User Pool, but instead the ARN to the pool itself:
await Auth.federatedSignIn(
{ token: id_token, expires_at: expires_in }
);
await Auth.federatedSignIn(
cognito-idp.${config.cognito.REGION}.amazonaws.com/${config.cognito.USER_POOL_ID},{ token: id_token, expires_at: expires_in }
);
AWS asks "What 3 things do you want to see in Amplify this year?" Respond at https://twitter.com/undef_obj/status/1217667714413551617
Has anybody else experienced this?
@ajonp roles aren't required because you can expose your api to public access via IAM, or Apikey. It sounds like you need to allow your role to use specific queries and mutations with inline policies.
Hi guys, who knows how to solve this problem.I encountered a problem when using the aws cloudformation plugin. After writing the configuration, "Failed to create stack: test-1. Reason: Detailed Message: Requires capabilities: [CAPABILITY_AUTO_EXPAND] (Service: AmazonCloudFormation; Status Code: 400; Error Code: InsufficientCapabilitiesException; Request ID: b34897e5-69f4-47db-b054-ca769208a540) "
@Rafcin I guess that maybe he meant the role assigned to the Amplify CLI user, which needs some roles to create the resources. @ajonp, maybe you can be allowed to run your project in a separate AWS account? At least for a trial, then log all AWS API requests with CloudTrail to see exactly what a custom role would need to be created in the customer account.
I am also facing same issue connecting to angular appsync
I am not having another problem, where a deployment from a GitHub branch never finishes building due to my React app not finding
aws-exports, but it does while local dev
this SO entry describes my exact problem https://stackoverflow.com/questions/59708481/aws-amplify-deploy-failure-due-to-aws-exports
any pointers extremely appreciated
for the record,
amplify publish deploys just fine
.
L
Hey Everyone- A noob at AWS lambda/amplify etc. world but have been able to get a few toy things launched. Major kudos to Nader Dabit (a genius, huge fan) and everyone else at AWS who make this technology accessible to even the common solo entrepreneur. Since I am in mainland China and it doesn't seem we will get amplify anytime soon, does anyone have trailheads on how to do similar with cognito, and the other services? I am a user of dokku/docker containers on AWS Beijing, but would like to start creating lambda based stuff. Is it a matter of terraform or ansible coordination? I am a bit out of my element. Thanks in advance!
I should mention, websites can't be served from s3 due to government regulation even though I have a fully registered local company and the required government license for a website.
Does anyone know if there's a way to skip a build in Amplify Console?
Hi All. I have two separate amplify projects - one built with React-Native which has its own Cognito user pools, DB, etc and another independent project for React (Admin console) with its own user-pools, DB etc.
How can I share the database (GraphQL via Amplify API) from one project to the other? Backend is DynamoDB
Hi All. I have two separate amplify projects - one built with React-Native which has its own Cognito user pools, DB, etc and another independent project for React (Admin console) with its own user-pools, DB etc.
How can I share the database (GraphQL via Amplify API) from one project to the other? Backend is DynamoDB
Ah - found out how to do it - simply switch the endpoint and run amplify configure
Then switch it back again afterwards....
but have set up the configuration and used Amplify.configure()
@jimjiminyjimjam_twitter I think you can manually do something like this:
Amplify.configure({Analytics: { AWSPinpoint: { appId: 'YOUR EXISTING PINPOINT ID', region: 'YOUR REGION'} } } ); https://aws-amplify.github.io/docs/js/analytics#manual-setup
