ability to expose devfile endpoint without authentication requirement?
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
We are facing an issue where we cannot run our server software during development in gitlab-workspaces, since it will try to self-check and fail because it is missing the authentication cookie for the workspace. From what I can tell, the authentication cookie is not optional and always required. Is there any intended way that I am missing to reach endpoints exposed through the gitlab-workspaces-proxy from other clients than the developers browser?
I currently see no "good" way other than supressing that self-check, since there is neither a way to get a valid authentication token inside the workspace nor a way to supply it to the server check.
We are trying to run remix with live reload, which will reach out to itself through the same url that it passes to clients to connect back to (the endpoint specified in the devfile, like https://3001-workspace-xxx-yy-zzzzzz.workspaces.cluster.example). Since the request is done by the server, there is no authentication header set (unlike for the requests originating from the browser/development client) and it will get redirected to the login page, failing the selfcheck and aborting the server start with an error.