- Newest
- Most votes
- Most comments
Hello,
I understand from your query that you found that LOGIN [1] endpoint's response is URI decoding your state parameter from "%3D" to "=". However, your framework with Springboot requires/expects "%3D" to come back, and not an "=" and presence of "=" in your state is prompting an error with your framework. Additionally, AUTHORIZATION [2] endpoint is working fine which returns back the "%3D" meaning it keeps the encoding intact.
Based on your comments, I was able to replicate the same by capturing two HAR [3] files (in Chrome browser) for logging the LOGIN flow vs AUTHORIZATION Flow in us-east-1
region
- With
LOGIN
flow, the response has decoded%3D
to=
for the state parameter. - However, with AUTHORIZATION flow, the
%3D
remained intact in response as well.
Hence, I checked in with the Cognito service team internally on your behalf, but they currently require your AWS account information alongside the UserPool information to help us assist you on this query. However, please do not post any such sensitive information over re:Post since this is a public platform.
Therefore, I would like to request you to log a support case directly with our Premium Support team, who can help you in getting the requested information to the service team securely.
As always, feel free to reach back out with any further questions or concerns in the meantime!
References:
[1] https://docs.aws.amazon.com/cognito/latest/developerguide/login-endpoint.html
[2] https://docs.aws.amazon.com/cognito/latest/developerguide/authorization-endpoint.html
[3] https://aws.amazon.com/premiumsupport/knowledge-center/support-case-browser-har-file/
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago