- 最新
- 投票最多
- 评论最多
Hello.
When you encounter a 401 status code, it typically means "Unauthorized", suggesting that there might be an authentication or authorization issue.
If your application uses tokens for authentication (e.g., JWT tokens), ensure the token hasn't expired. Also, check if the token is being sent correctly in the request headers.
If you're using AWS Cognito for user authentication:
- Ensure the user is authenticated correctly.
- Check if the user's role has the necessary permissions to perform the query.
- Make sure the user pool and identity pool configurations haven't been accidentally changed.
Regards, Andrii
Absolutely, if your primary issue revolves around the queries post-authentication, it's worthwhile to focus on the intricacies of user pool and identity pool configurations. Here are specific areas to check in AWS Cognito:
Cognito User Pool:
a. App client settings: Make sure that the associated AppSync API is still selected under the "Enabled Identity Providers" section.
b. OAuth 2.0: Ensure that the callback and sign out URLs are still correctly configured if you are using OAuth.
c. Token expiration: By default, Cognito User Pools generate tokens that last for 1 hour. Ensure that the token hasn't expired when you are trying to make a query.
Thank you, I have doubled checked all those points you have listed and it looks like my settings are all configured correctly . I am still not sure why the issue is happening
相关内容
AWS 官方已更新 2 年前- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
Is there anything specific about the user pool and identity pool configurations to check? I know I didn't update these settings at all since when the queries were working , and when they stopped working. I also noticed that I am able to sign in and sign out a user just fine. It is just when it attempts to perform a query. My user is signed in when it attempts to do a query. Please kindly clarify specific settings to check for .