Basic Auth is a simple HTTP authentication mechanism in which a username and password are typically requested before the application is served. In the context of Central Command, Basic Auth can secure the protected app area at the reverse-proxy level — in addition to the subsequent user sign-in with JWT inside the application.
This dual structure has a clear purpose: the public website remains reachable and indexable, while sensitive UI paths are not exposed unfiltered on the internet. Basic Auth is not a substitute for fine-grained permissions in the app but a first hurdle. Passwords should be strong, be given only to authorized people, and be rotated when needed.
In everyday use this means: whoever opens the backend may first pass the server-level protection and then the application login. API routes for JWT must not be blocked by the same Basic Auth conflict. The architecture therefore cleanly separates public marketing paths, the authenticated API, and the protected UI — Basic Auth is just one layer of it.
