No answer on important GitHub issue after one month (We even offered a PR)

[tbrodbeck]

Hi!

About a month ago I created a very detailed, minimal and reproducible issue detailing a bug in Keycloak that actually affects our users and ultimately leads to user loss: ForkFlowException: Repeated AUTH_SESSION_ID on forgot-password (user resets password twice in a row) · Issue #39970 · keycloak/keycloak · GitHub

Would be very important for us to at least get some quick feedback on that matter! We even offered to create a Pull Request with a fix ourselves - so we would do all the heavy lifting - but still we did not receive a single answer.

I can understand if there are currently some more urgent security topics that might be prioritized. Would be great if some maintainers could step in for a feature review so we can get this recurring issue fixed for everyone. Especially now when more and more people will use shared browser sessions (Custom Tabs on Android) this issue will be more and more important to fix.

Cheers!
Till Brodbeck

[xgp]

@tbrodbeck This is a community forum, and is not frequented by the Keycloak maintainers.

Per your comment

Does it help if we would create a PR with a fix ourselves?

I’ve found that the answer to this is “yes”, as the maintainers are busy, and have lots of priorities that never seem to overlap with mine. My experience is that a correct, well-reasoned, thoroughly documented issue (as yours is), followed by a PR that solves the exact issue you have raised, is likely to get reviewed and merged.

Good luck!

(by the way, this is awesome. I can’t stop laughing)