With Jenkins, you can use the PowerShell Plugin to have jobs executing PowerShell scripts. You can also use the Credentials Binding Plugin to pass in usernames/passwords, that are stored on Jenkins in an encrypted credential store, to your scripts!
I wanted to make this short post to show how easy it is to take advantage of credentials that can be used by multiple jobs, and only have to change them in the credential store (as opposed to changing their value in every single job).
When the proper plugins are installed on Jenkins, new jobs should have the ability to pass bound credentials into your scripts (be it PowerShell, bash, etc.) as environmental variables. Your jobs will have a Use secret text(s) or file(s) checkbox that, when checked, provides the ability to select the types of bindings you are using. In my case in the screenshot below, I pass the Username and Password (separated) credential option, as to provide two separate environmental variables into the script:
Now your scripts can have credential objects passed to them, if they have -Credential parameters that can take the appropriate object types. You would create credential objects as so:
Premise: Death and birth certificates can be filed online, with practically no oversight. DefCon Response: Let’s show the world how easy it is to kill anyone, and/or profit from the birthing/killing of virtual…babies?
This is one blog article in a series titled the DefCon 23 Debrief Series. This year was my first year at DefCon in Vegas, and it was awesome. If you ever have the opportunity to get your work to ship you there? Take it. If you ever get the opportunity to ship yourself? Don’t think. Go.
Premise: Let’s place a computer on a gun, and give it WiFi. DefCon Response: Let’s hijack it, and install our own malicious updates.
This is the first article in a series titled the DefCon 23 Debrief Series. I may be doing one or more further articles, given time. This year was my first year at DefCon in Vegas, and it was awesome. If you ever have the opportunity to get your work to ship you there? Take it. If you ever get the opportunity to ship yourself? Don’t think. Go.
This week, Twin Cities PowerShell had Michael Greene and Mark Gray from the Microsoft PowerShell Team speak to the user group! There was quite a bit of content, so I’ve put together a summary of everything we had gone over — with a ridiculous amount of resource linkage:
This is just a quick blurb, but you may have wanted a nice way to query the Unix Attributes tab of AD accounts. Using PowerShell, and the ActiveDirectory Module, you can pull these values quite easily. The AD property names are listed above each box in this example:
I recently started learning about Sumo Logic and playing around with it’s log aggregation capabilities. I thought it would be cool to create a PowerShell Module to work against the APIs, as Sumo Logic takes an interesting approach to log aggregation.
I recently found myself using a hard-to-find OfficeScan Database scanning tool that reports any issues it finds within the OfficeScan Server application directory. I thought it would be great if I could automate/schedule the tool, but the tool is only an executable that works only in interactive mode with a GUI. Thankfully, I found that these issues are all problems that can be discovered via PowerShell script! So I created a PowerShell version of the tool.