Issue with Discourse as SSO provider & Social Sign Up

Is this bug that unimportant to be ignored again?

I reported a similar issue in January but here you can see a minimalist reproduction with nothing else with vanilla discourse and an official SSO implementation. If anything, I would like someone to either acknowledge there is a bug or saying what we’re doing is wrong.

How do we get attention to this issue? Is it possible to hire team members if money is an issue?

– A frustrated client & dev.