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 invoking CMD/PowerShell via Automate instead of Control #27

Open
jasonrush opened this issue Oct 14, 2019 · 6 comments
Open

Allow invoking CMD/PowerShell via Automate instead of Control #27

jasonrush opened this issue Oct 14, 2019 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@jasonrush
Copy link
Contributor

There is the known issue where the Control API does not support 2FA/MFA authentication, which limits a reasonable number of people from using the Invoke-ControlCommand function. We have the ability to implement similar functionality (though maybe not as efficient execution) via the Automate Computers/$computerID/CommandPrompt endpoint.

This can be assigned to me, as I intend to work on implementing this.

@dkattan
Copy link
Collaborator

dkattan commented Oct 15, 2019

A few things to consider on that endpoint:

  1. It’s slow
  2. I think you can break it by having !!!! in your script
  3. Automate doesn’t have MFA for their endpoints either

@dkattan
Copy link
Collaborator

dkattan commented Oct 15, 2019

How would you guys feel about creating a custom extension for Automate and/or Control that would allow us to create our own auth methods and bypass a lot of the issues we encounter?

@jasonrush
Copy link
Contributor Author

For what I'm doing/needing, I'm fine with slow and inefficient if slow and inefficient in terms of PS/Automate is still substantially faster than using Control to manually log into each server, open a powershell prompt, paste code that stores results to file/etc, copy results back to local computer, and compile all the results manually.

Are you saying a single ! or specifically 4x !!!!? Either way, something with a few limitations at this point is better than me doing everything manually.

And what do you mean regarding Automate not having MFA for their endpoints either? I'm new to the plugin architecture, but my understanding is that the Control plugin doesn't give a way to provide MFA tokens, but depending on configuration may require MFA to actually do the actions you've told it. With the built-in Automate functionality, it's using your Automate API session and no further MFA tokens/etc are required while the session is active.

Ultimately this project is up to you guys for decisions/etc, I just want to provide my feedback on where my use cases may vary. If you guys ultimately decide not to include this functionality, I'll just maintain my own separate plugin that extends this one, and will still help with improvements to the main plugin here where I'm able.

@gavsto gavsto added the enhancement New feature or request label Jul 4, 2020
@gavsto
Copy link
Owner

gavsto commented Jul 4, 2020

I am adding this as a feature request because I absolutely think it should be done, even if it is slow.

@DarrenWhite99
Copy link
Collaborator

This is being developed and will be committed publicly "soon".

@DarrenWhite99 DarrenWhite99 self-assigned this Jul 22, 2020
@DarrenWhite99
Copy link
Collaborator

This functionality is available in the "AutomateCommand" branch.

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

No branches or pull requests

4 participants