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

Support plain text file cache fallback in headless linux #410

Open
kyle-rader-msft opened this issue Sep 19, 2024 · 5 comments
Open

Support plain text file cache fallback in headless linux #410

kyle-rader-msft opened this issue Sep 19, 2024 · 5 comments

Comments

@kyle-rader-msft
Copy link
Contributor

I've been using azureauth in Wave Workspaces (a C+AI alternative to microsoft devbox) where you connect via VSCode to a Linux VM. Azureatuh can be installed here, and ... through VSCode, it actually can already launch a web browser auth prompt! Which is great!

The problem is that you get the cache persistence check failures, because it's headless. And there is no cache. Meanwhile, the git credential manager in the same environment, is not launching a web prompt and forces me to do device code login - but it caches in a plain text file, so it doesn't prompt after that.

It would be great to have azureauth also allow a plain text fallback in this scenario.

@mvanchaa
Copy link
Contributor

But @kyle-rader-msft wouldn't that be a security issue as it's a plain text?

@kyle-rader-msft
Copy link
Contributor Author

kyle-rader-msft commented Sep 25, 2024 via email

@rewrlution
Copy link

Hey @kyle-rader-msft , I am Huijing.

It would be great to have azureauth also allow a plain text fallback in this scenario.

Am I reading your feature request correctly that you want us to persist access token in plain-text file just like what Git Credential Manager does?

@kyle-rader-msft
Copy link
Contributor Author

kyle-rader-msft commented Sep 25, 2024 via email

@AtOMiCNebula
Copy link

Allowing an opt-in to plaintext credential caching is fine IMO, though I'm not confident enough in the space to want to suggest making it default behavior. Perhaps naming the setting something like "allow plaintext cache storage"? Ultimately, as long as the cache file itself is only user-readable (and not group/world-readable), then that seems pretty reasonable to me.

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

No branches or pull requests

4 participants