Closed marcolino closed 3 years ago
I could solve myself at last... :-)
It was simply the redirect
to home, when landed on /oauth2
, that destroyed the auth in localstorage...
Now I setup oauth redirect_uri to https://example.com/
, instead of https://example.com/oauth2
... :-)
Sorry, everybody.
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.
Before opening, please confirm:
JavaScript Framework
React
Amplify APIs
Authentication
Amplify Categories
auth
Environment information
Describe the bug
Auth.federatedSignIn returns correctly (after asking for user permission in the oauth window), but the
cred
payload is undefined.Using Auth.signIn works just fine, and I get the user credentials and details in the
then
payload, as expected.I call
Amplify.configure()
this way:and
Auth.federatedSignIn()
this way:I get into the federatedSignIn callback, with an undefined
cred
.I did also try to listen on Hub (which too works for email/password logins), with no success.
I did also set window.LOG_LEVEL = 'DEBUG', so I include the DEBUG logs:
Expected behavior
I'd expect to get the authenticated user info, like I get with Auth.signIn()
Reproduction steps
Proceed with a basic aws-amplify setup; I did follow this post: agnita-authentication-for-create-react-app-using-aws-cognito.
Code Snippet
Please ask me for any additional code that can be useful to solve the issue, I'll be glad to share it...
Log output
aws-exports.js
No response
Manual configuration
Additional configuration
$ aws cognito-idp describe-user-pool --user-pool-id eu-west-1_edKzSSeU9
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response