2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Ok, I found an answer to this. Here's a github issue that amplify-js team was nice enough to field for me.
https://github.com/aws-amplify/amplify-js/issues/11197
Restricting access by "Authenticated user" - "User needs to sign in to use the REST API" will NOT authenticate any users who have been added to a "group". Users in "groups" need to have one or more of their Groups explicitly added to the authentication.
répondu il y a un an
0
Is it possible you have 2 Cognito user pools? Pool A was created with your original API, and Pool B was created with your new API? That would explain the behavior with existing users. If that is the case, I think you can run amplify import auth
and import the first pool.
répondu il y a un an
Contenus pertinents
- demandé il y a 2 mois
- Réponse acceptéedemandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
Thanks for the prompt reply. This is not the case. Both old (Pre-API Deploy) and new (Post-API Deploy) users can log into the app and are contained in the same user pool. I've tried fresh incognito browsers to see if it's cookie or cache related with no help. I'm not clear how authentication is deployed via Amplify in this case. How can I troubleshoot this?