Replies: 2 comments
-
We do support user/password as well (common option when not using token for jupyter). For other auth schemes there is an API that you could write an extension to support (and it supports timeout). There's an example here of using it: The Azure ML Extension in VS code uses it to provide connections to jupyter servers behind an Azure proxy. |
Beta Was this translation helpful? Give feedback.
-
The root of the API is the 'registerRemoteServerProvider' function. vscode-jupyter/src/platform/api.ts Line 42 in 1143125 You call this from your extension. You can see the implementation of the remote server provider in the example here: It is returning an object that has the authorization headers for the request and a timeout that causes the jupyter extension to reask later. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
connecting VS Code notebooks to a remote server works really nice. However, right now , the expectation is that the authentication is exclusively done via ?token as a query param to the url.
Some cloud vendors hosting Jupyter Notebooks are using alternative auth schemas however and that prevents using VS Code NBs in that case.
I wondered if support for additional auth schemas could be added. The jupyter community also did that in the Jupyter Server Gateway component: jupyter-server/jupyter_server#529
As tokens might time out, it would be even better if it would be possible to register a callback function like getAuthHeaderForOutboundCall that users can implement on their own. (In there, the auth tokens could be recreated from an api key for example if they time out)
Beta Was this translation helpful? Give feedback.
All reactions