Auth - federatedSignIn - add additional validationData
See original GitHub issueIs your feature request related to a problem? Please describe.
I would like to add some validationData
on Auth.federatedSignIn()
so that i can access this data on some Cognito triggers like Pre authentication
or Post authentication
.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:15 (2 by maintainers)
Top Results From Across the Web
Authentication - Advanced workflows - JavaScript - Amplify Docs
Learn more about advanced workflows in the Amplify auth category. ... federatedSignIn() to get AWS credentials directly from Cognito Federated Identities ...
Read more >Amplify Federated Sign In not returning Email for Facebook
The issue was with <amplify-facebook-button> since it uses Identity Pool workflow instead of User Pool workflow. Creating a custom button with ...
Read more >Authentication - Test Page
Amazon Cognito Federated Identities on the other hand, is a way to authorize your users to use the various AWS services. With an...
Read more >Customizing user pool workflows with Lambda triggers
Create Auth Challenge, Creates a challenge in a custom auth flow ... Federated sign-in does not invoke any Custom authentication challenge Lambda triggers, ......
Read more >How to use the @aws-amplify/auth.federatedSignIn function in ...
'function' ) { throw new Error( 'No Auth module found, please ensure @aws-amplify/auth is imported' ); } await Auth.federatedSignIn( 'google', { token: ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s been almost two years since this ticket was open, it’s really a very important feature to build production-ready sign-in/signup pages using a CAPTCHA. That will be great to get at least feedback whether you are planning to implement it or not, this will give us the opportunity to think about other solutions like AWS WAF CAPTCHA (not cost-effective for our use case) or move to another IDP.
Is there any update on this?