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

Suggestiong on Credential Management #1

Closed
JonnMsft opened this Issue Feb 21, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@JonnMsft

JonnMsft commented Feb 21, 2017

Great stuff Jan! You might try using the default credential management, at least for the Scheduled Task case. Once you call Connect-Tesla without the -NoProfile parameter, the encrypted credential is stored in the user profile for the currently logged-on user. I suspect that you can skip Connect-Tesla entirely as long as the task runs under that same credential. I can't speak for Azure Automation.

@janegilring

This comment has been minimized.

Owner

janegilring commented Feb 21, 2017

Ah, didn't know that...thanks!

@janegilring

This comment has been minimized.

Owner

janegilring commented Mar 4, 2017

A note about the module's built-in support for persisting credentials is now added to the intro article

@janegilring janegilring closed this Mar 4, 2017

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