Hm okay.
So as mentioned its not a website that Discourse will be sending the info to.
Its a game server - aka just a VPS with MySQL running on it.
The old workflow was this:
Unity populates the SQL tables when users “register an account”.
What I’m looking to do is use Discourse as the registration and account management provider.
I.e they register with Discourse and use this info to log in to the game server (through the Unity client).
So I need a way of reliably transfering the Discourse user data to the MySQL database.
(Theyre both on the same machine).
For this we have set up a foreign data wrapper for Postgres → Mysql, and then triggers to populate appropriately.
Then when the user enters their (Discourse) email and password in-game, theyll be able to login - theoretically.
The other issue I have recently read about was the password hashing used by Discourse (which is a good thing for many reasons), but means hashes are unique so cant do that way.
So again, theres no website for the SSO, only Discourse and another VPS running the video game server that clients connect to.