Comments (10)
@ottokruse This issue was linked to setting the wrong client_id for cognito in netlify. The correct id has been set for the env vars and the solution works as intended.
Apologies for the inconvenience!
from amazon-cognito-passwordless-auth.
Best check the logs of the Verify Auth challenge lambda function? It's that lambda function that reports it does not have access in your message. Hopefully the stack trace in the logs reports what the lambda function was doing. Otherwise set loglevel to Debug.
Looks like it's unrelated to the Netlify move by the way?
from amazon-cognito-passwordless-auth.
The Verify Auth challenge lambda function is never invoked, all we get is a 400 response with the error message provided above. The log_level is already set to DEBUG
from amazon-cognito-passwordless-auth.
Hard to follow what it happening. Maybe the User Pool does not have permission to invoke the lambda function. This permission is created automatically by the CDK stack but maybe got inadvertantly removed. (Still I see no reason why this would be related to a move from S3 to Netlify)
from amazon-cognito-passwordless-auth.
Maybe of help: https://stackoverflow.com/questions/42460846/when-i-try-to-login-using-aws-cognito-i-get-an-accessdeniedexception-about-my-cu
from amazon-cognito-passwordless-auth.
Any luck @seel93 ?
If not can you provide more details? Eg show how you use the Passwordless construct and how you deploy. Ideally we can reproduce. Also, what version of the passwordless lib are you on ?
from amazon-cognito-passwordless-auth.
We're only using a small part of the code in this repo and using terraform instead of the cdk.
Magiclink is currently the only sign-in method we're using, and code for all the other methods is not a part of our repo.
This solution was working fine with s3 and cloudfront, and when we introduced Netlify the verifyAuth trigger failed to run.
I don't have the passwordless lib version in front of me right now, but will provide it asap.
from amazon-cognito-passwordless-auth.
@ottokruse we're using v0.5.1 of the passwordless lib
from amazon-cognito-passwordless-auth.
Check the resource based policy statements of the VerifyAuth lambda in the AWS console and make sure correct?
Should be something like:
![image](https://private-user-images.githubusercontent.com/6275520/249425315-7395d42a-c246-401a-b50c-5e2588ffb1d4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQzMTYxNjUsIm5iZiI6MTcyNDMxNTg2NSwicGF0aCI6Ii82Mjc1NTIwLzI0OTQyNTMxNS03Mzk1ZDQyYS1jMjQ2LTQwMWEtYjUwYy01ZTI1ODhmZmIxZDQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgyMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MjJUMDgzNzQ1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZDUyMWMzNDU1MDAwYWIzYmI0NzQyMjc5ODk1MzMzYjM1MzFhOTBiMmJjMTIwZGI0ODU0YzdiNWNhNTZhMmNlZCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.hnFxQnI8l4p5mB9mhYszs5M9sdwhGQcbUEAXstZC4dw)
And when opened:
from amazon-cognito-passwordless-auth.
Yes, I have the exact same policy. I'm assuming our webapp hosted in s3 wouldn't have worked without it
from amazon-cognito-passwordless-auth.
Related Issues (20)
- Passwordless.configureFromAmplify() no longer works with the latest version of Amplify (v6)
- Type error in Verifying FIDO2 Challenge Response HOT 6
- Usage of stepUpAuthenticationWithSmsOtp in plain web. HOT 5
- Feature request: HOT 1
- Amplify cli end-to-end example HOT 5
- [Question] Using Fido2 credentials for non-signin challenges HOT 1
- Prominently mention JWT/localStorage issues in FAQ -- Avoid JWT? HOT 6
- signInStatus is 'NOT_SIGNED_IN' during refresh of token HOT 3
- Dependency issue while implementing this tutorial HOT 4
- FrontEnd Shows "Unexpected End of JSON Input" HOT 8
- The example don't work corrrectly with Windows Hello through PIN authentication HOT 17
- [Feature] Provide a python package HOT 1
- Resetting state HOT 4
- Magic Link Metadata Storage HOT 8
- ReferenceError: debug is not defined HOT 1
- [Bug] Magic link abuse by authorized user HOT 9
- [Feature Request] Add OTP SMS authentication HOT 5
- Can we load logo from assets folder locally HOT 4
- Prevent users from self-edit attributes HOT 6
- [Need Help] - No "exports" main defined in ../node_modules/amazon-cognito-passwordless-auth/package.json HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from amazon-cognito-passwordless-auth.