You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some services it is required that some of their endpoints are accessible without authentication. A concrete example is the ml-workspace (https://github.com/ml-tooling/ml-workspace). For its "Setup SSH Access" feature it provides a small command that should be run in your local terminal like this:
However, the curl command fails, as there is no authentication header or cookie set. Do you have any idea on how this problem could be solved? Maybe there could be a way to disable the authentication for specific endpoints in the service configuration or some default /public endpoint is always served with no authentication?
Alternatively, we could also say that this is not supported and instead services like the workspace should be able to pick up the access token from an environment variable and integrate it into the command?
The text was updated successfully, but these errors were encountered:
I am wondering whether it's possible to set the authentication header / cookie in the curl command? I think you get the token in the cookie section of the browser or by login via command line.
For some services it is required that some of their endpoints are accessible without authentication. A concrete example is the ml-workspace (https://github.com/ml-tooling/ml-workspace). For its "Setup SSH Access" feature it provides a small command that should be run in your local terminal like this:
However, the curl command fails, as there is no authentication header or cookie set. Do you have any idea on how this problem could be solved? Maybe there could be a way to disable the authentication for specific endpoints in the service configuration or some default /public endpoint is always served with no authentication?
Alternatively, we could also say that this is not supported and instead services like the workspace should be able to pick up the access token from an environment variable and integrate it into the command?
The text was updated successfully, but these errors were encountered: