Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide an authentication and secrets mechanism for database access #992

Open
jonsequitur opened this issue Jan 20, 2021 · 4 comments
Open

Comments

@jonsequitur
Copy link
Contributor

In order to prevent people from having to paste connection strings into notebooks, we should have proper authentication support. This could include:

  • Aliases for connection strings that can be referenced from with the #!connect magic command.
  • AAD auth flow.
@jcmrva
Copy link

jcmrva commented Apr 15, 2022

It would be great if we could use the dotnet user-secrets tool with notebooks.

@brettfo
Copy link
Member

brettfo commented Jan 24, 2023

Thinking a little more broadly than databases, could we possibly get auth tokens via RequestInput and a specific value for inputTypeHint? VS Code extensions can provide authenticators, so if inputTypeHint was "token:github", the VS Code extension could get the GitHub auth provider (if installed) and try to get a token directly from that. We even have a good fall-back story, where if the requested auth provider isn't installed and we can't automatically get a token, we can simply prompt the user for a value. In the Jupyter Lab case we could simply fall back to the Jupyter method of prompting for input, and in the console/automation case, we could pull the value from a command line argument.

@jonsequitur
Copy link
Contributor Author

The input type hint system was intended to be used this way, so now it's hopefully just a matter of building the providers.

@jonsequitur
Copy link
Contributor Author

This work depends on #3567.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants