Open
Description
Before opening, please confirm:
- I have searched for duplicate or closed issues and discussions.
- I have read the guide for submitting bug reports.
- I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
JavaScript Framework
React
Amplify APIs
Authentication
Amplify Categories
auth
Environment information
# Put output below this line
Not relevant
Describe the bug
When Cognito user pool client id changes, new sign-in tries to create new cookie elements. Eventually it gets larger. Then CloudFront blocks it.
One possible solution would be clearing all Cognito related cookies before new signin.
There are already two tickets for this matter. But Amplify team seems ignore them. Not customer obsessive :)
Expected behavior
No server-side error must happen.
Reproduction steps
To reproduce:
- Log in to your app using Cognito.
- Change the client id in Cognito.
- Login again.
- Repeat 1.
After 3rd iteration you get the error message from the CloudFront.
Code Snippet
// Put your code below this line.
Log output
// Put your logs below this line
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response