-
Notifications
You must be signed in to change notification settings - Fork 38
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
Add install active directory install command #24
base: master
Are you sure you want to change the base?
Add install active directory install command #24
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a great add.
Sorry this got delayed, more testing is in progress. Posting a couple initial thoughts.
b17af3a
to
5a43e3b
Compare
5a43e3b
to
3bba31d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Testing looks good, just the one question here about using a hardcoded configuration password.
|
||
# Configuration | ||
$domain = "demo.local" | ||
$plaintextPassword = "vagrant" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this get the VM password from the launch config for manageServices.py
? I don't mind a hardcode value however I that is not super friendly to the those that may want to have at least some security
in the testing env.
Adds install active directory command script to vm-automation; which allows for testing Kerberos/AD environments
My testing steps were running this script locally against a windows 2016/2019 server box. Will be used by https://github.com/rapid7/metasploit-jenkins-jobs/pull/449
I then tested it with vmware-automation project by first building the metasploit-baseline-builder docker container:
Creating an ESXi config in
~/helper_config.json
:Running a docker container from the Jenkins user, mounting vmware-automation and the esxi config:
Inside the running docker instance I had to install pip:
Verifying the action is available (change the prefix):
Running the action with hard coded user/password values against the target machine (change the prefix):
View the log files: