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

Allow 'run as' user and password to be specified for window_certificate #511

Open
MattFenner opened this issue Nov 7, 2017 · 1 comment
Labels
Status: Sustaining Backlog An issue ideal for the Sustaining Engineering team (or anyone else if they want to adopt it). Triage: Feature Request Indicates an issue requesting new functionality.

Comments

@MattFenner
Copy link

It would be great to have the ability to run the windows_certificate resource as another user like you can with execute resources.

this would let you put a certificate into another users store (if you have the username and password).

I imagine it is pretty easy as it is just passing the details through to the embedded powershell script

thanks

@tas50 tas50 changed the title Feature Request: allow 'run as' user and password to be specified for window_certificate Allow 'run as' user and password to be specified for window_certificate Mar 2, 2018
@tas50 tas50 added the Status: Sustaining Backlog An issue ideal for the Sustaining Engineering team (or anyone else if they want to adopt it). label Feb 2, 2019
@tas50 tas50 added Triage: Feature Request Indicates an issue requesting new functionality. and removed Type: Feature Request labels Apr 5, 2019
@xorima
Copy link
Contributor

xorima commented Sep 30, 2019

Why not just use ACLs to allow the other user to access the key from the machine level store?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Sustaining Backlog An issue ideal for the Sustaining Engineering team (or anyone else if they want to adopt it). Triage: Feature Request Indicates an issue requesting new functionality.
Development

No branches or pull requests

3 participants