[NathanKP]

Thanks for the report! I'll keep an eye on it. So far we aren't seeing any other reported issues, so it's possible that a browser extension, or something else in your setup is messing with the SSO flow.

Redirect back to localhost:3128 is normal, that's where Kiro is watching for a callback, but the missing state is not normal. Something may have stripped the info out of the callback before it occurred, which is why I suspect an extension in your browser.

Will keep an eye on this though!

[homami]

It is also not working for me, this opens http://localhost:3128/oauth/callback?code=... but on Kiro interface I see "There was an error signing you in. Please try again"

[DividableMiddle]

Same error as the others. Looks like auth is successful in popup window: "You can close this window".

Then in Kiro I see "There was an error signing you in. Please try again.".

FWIW, I've tried GitHub & Google, in different browsers, on different networks.

[DividableMiddle]

For me, it was Little Snitch blocking the request..

[CoolCold]

isn't 3128 port is mostly used by proxies (squid and alike)? https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbe...

I personally run my proxy there and overall I'd take some > 10000 port for such kind of stuff

[cl0wnshoes]

FWIW Github login worked, only extensions I run is a password manager and Kagi.

[Imustaskforhelp]

After you said that google login didn't work, since I had also used github login, I wanted to tell that github login had worked for me, but you beat me to it!

I think Auth can be a bit of mess, but yes Its still absolutely great that I can just login with github and it just works, I am trying out Kiro right as we speak!

[NathanKP]

Thanks for the additional info!

[ric99915]

For me even Github doesnt work

Same error as for Google