Put admin dashboard and used graphql queries/mutations on separate domain/path

[ideallical]

Put admin dashboard and used graphql queries/mutations on separate domain/path

[nick-funk]

Putting the admin UI behind a VPN will unfortunately not add any security to your setup.

Both the admin and client speak to the graphql API which must remain public. Even if the Admin UI is hidden behind a VPN, all of the admin API functions in graphql would still be public as the API must remain public for the stream to function. As well, the stream has moderation actions that can be performed while a mod/admin is logged in stream side, so the public stream, has to have API access to moderation abilities, which again, must be public.

The most common attack vector for Coral is not the admin UI, but the API itself. We would have to refactor the entire Coral monolith into two separate graphql API endpoints to truly create the security blanket you are wanting. That would take an incredible amount of work, and it is far easier for us to just have a public graphql API and perform thorough pen tests (which we do regularly) to ensure that none of Coral is vulnerable to attack instead of trying to rely on a VPN to protect the data.

I hope that answers why Coral is architected the way it is and why we can't put the admin behind a VPN.