CORS issue in new deployment

[Robert-Tweedy-Emory]

Using a fresh installation of the Vortex components (aclcore, aclapi, backend, frontend) with minimal customization (only edited the various config.yaml files & Systemd service files as needed to start the services) I'm unable to successfully log in to a testing environment with vague error messages printed by the web browser (Firefox 128 ESR; also tested with Chromium 140 and seeing similar results). Further inspection seems to indicate that this is a CORS issue and that the appropriate headers are missing from the response generated by the backend component, hence why I've opened the issue in this repo rather than the Frontend repo.

Environment:
Backend & Frontend are running on the same Rocky Linux 8.10 VM (IP Address: 192.168.9.3) for testing purposes.
Testing environment is using plain HTTP & a disposable test account (so that legitimate passwords are not being sent unencrypted over plain HTTP).

An example error message from the Chromium web developer tools console: Access to fetch at 'http://192.168.9.3:8080/auth/login' from origin 'http://192.168.9.3:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

[PythonHacker24]

The CORS issue might be due to the backend having a hardcoded CORS policy allowing only localhost and similar addresses. I would need to add it to config.yaml. This was a classic issue during the development process. Let me go through fixing it.

[PythonHacker24]

Here, I had it as a todo to add it in config file

[PythonHacker24]

Fixed the CORs issue and pushed to development-v2 branch. CORs are now configured in config.yaml.