Closed cojack closed 5 years ago
@cojack from your description I can tell you are federating with the Cognito User Pool. If so, you should not use Auth.federatedSignIn()
as this method is used to federated with the Cognito Federated Identity Pool: https://aws-amplify.github.io/docs/js/authentication#federated-sign-in
In order to use the Facebook as the provider of the Cognito User Pool, you should use Cognito Hosted UI: https://aws-amplify.github.io/docs/js/authentication#using-amazon-cognito-hosted-ui
@powerful23 then what should I do with the response tokens from URI fragment?
@cojack if you have followed the doc: https://aws-amplify.github.io/docs/js/authentication#using-amazon-cognito-hosted-ui, you will find out how to setup the app client and how to make it work using Amplify: https://aws-amplify.github.io/docs/js/authentication#make-it-work-in-your-app
Amplify will parse the callback url automatically and send a signIn
event when the url is correctly parsed.
@powerful23 its not working, I wrote that in first message at Additional . I got the same error: No current user.
@cojack
Even If I do it by Hosted UI, when It comes back from Hosted UI, there is no option to set access_token anywhere,
There is no need to set access_token
explicitly after coming back from Hosted UI, this process is done by Amplify library. The flow is: after coming back from Hosted UI to your app, you should listen on the signIn
event from the Hub
module. When the event is emitted, you can call Auth.currentAuthenticatedUser()
to get the current user.
@powerful23 and this is how I make it, it's not working, any other proposition?
@cojack can you paste the debugging info here? Especially the part when you get redirected back from the Hosted UI.
Hello everyone, we have created an RFC for feature work that should make the challenges found in this issue easier in the future. If you have a moment please read through the details and add any comments: https://github.com/aws-amplify/amplify-js/issues/2716
Your feedback in the RFC will help us ensure that we are delivering the best experience possible. Thank you.
Closing this issue. Please let us know you still have this issue.
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server *-help
channels or Discussions for those types of questions.
Describe the bug Hello my folks, Im facing really big issue with development, and I stuck for more than a week because I could not find ANY information how this suppose to work and it looks like is't not working at all in that flow.
So here we go.
To Reproduce Steps to reproduce the behavior:
Quick FAQ:
npm i angular-6-social-login
a) configure module as described here: https://www.npmjs.com/package/angular-6-social-loginhome.component.ts
and add this:Open
home.component.html
and add some where bellow<amplify-authenticator>
this line:<button (click)="socialSignIn('facebook')">Sign in with Facebook</button>
Open web browser at http://localhost:4200 and click on the
Sign in with Facebook
button, authorise you to your application.When it came back, you will se in console something like: "No current user", and I'm not able to make any request to the graphql resource.
Expected behavior I should works the same way as sign in by cognito user pool.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information): Not related.
Additional context
Even If I do it by Hosted UI, when It comes back from Hosted UI, there is no option to set access_token anywhere,
federatedSignIn
returns error with expired token.I need help.
You can turn on the debug mode to provide more info for us by setting window.LOG_LEVEL = 'DEBUG'; in your app.