Before opening, please confirm:
Operating System
Windows11
Kiro Version
0.9.40
Bug Description
On Windows 11 Enterprise, the Kiro IDE (v0.9.40) fails to process the authentication callback after a successful AWS IAM Identity Center sign-in. Although the IDE is correctly listening on port 3128 and the browser successfully redirects to http://localhost:3128/signin/callback, the IDE makes no further action and remains on the sign-in screen.
Technical logs show the TCP connection on port 3128 transitions from Listen to FinWait2 immediately after the callback request is initiated, suggesting the IDE terminates the connection prematurely without parsing the token. Notably, this exact same organization and proxy configuration works successfully on macOS.
Steps to Reproduce
- Launch Kiro IDE on Windows 11 and click "Sign in with AWS IAM Identity Center".
- Complete the authentication flow in the browser until the "You can close this page now" screen appears.
- Observe the browser network logs: A 302 Found status is recorded for the callback to
localhost:3128.
- Check the IDE state: The IDE does not react, and the local port status changes to
FinWait2.
Expected Behavior
The Kiro IDE should successfully receive and process the authentication token from the localhost:3128 callback. Upon receiving the data, the IDE should automatically transition from the sign-in screen to the logged-in workspace and display the user's projects/dashboard. The behavior should be consistent with the macOS version, where the handoff from browser to IDE occurs seamlessly.
Conversation ID
No response
Additional Context
No response
Before opening, please confirm:
Operating System
Windows11
Kiro Version
0.9.40
Bug Description
On Windows 11 Enterprise, the Kiro IDE (v0.9.40) fails to process the authentication callback after a successful AWS IAM Identity Center sign-in. Although the IDE is correctly listening on port 3128 and the browser successfully redirects to
http://localhost:3128/signin/callback, the IDE makes no further action and remains on the sign-in screen.Technical logs show the TCP connection on port 3128 transitions from Listen to FinWait2 immediately after the callback request is initiated, suggesting the IDE terminates the connection prematurely without parsing the token. Notably, this exact same organization and proxy configuration works successfully on macOS.
Steps to Reproduce
localhost:3128.FinWait2.Expected Behavior
The Kiro IDE should successfully receive and process the authentication token from the
localhost:3128callback. Upon receiving the data, the IDE should automatically transition from the sign-in screen to the logged-in workspace and display the user's projects/dashboard. The behavior should be consistent with the macOS version, where the handoff from browser to IDE occurs seamlessly.Conversation ID
No response
Additional Context
No response