How to pass multiple credentials to powershell script monitor

Hi,

I know it's possible to pass credentials as an argument that is assigned to the component in a PowerShell script monitor.

This way, I can use only one account in my PowerShell script. Is it possible to call other credentials from the SAM Credentials library?

I would need at least three different account in the same powershell script.

Find more posts tagged with

powershell monitor

Accepted answers

All comments

thomasdrinkwater

From my understanding this is not possible directly in SolarWinds to pass through multi-credential sets (would make for a nice feature).

The 1 account normally applied and as you've rightly stated calling that $user / $pass variable works.... when handling the multiple accounts, I have used the following method:

1. Use the Monitoring account as "cred 1"

2. Setup the other accounts to be stored in encrypted files (.bin, .dat etc)... And use either the local system account or strong certificate.

3. Call in the passwords as you need them in the script then wipe with $Pass = $NULL once the command has been completed.

SteveK

I was going to make the same recommendation as @thomasdrinkwater

As far as I know a powershell component can only have a single credential set applied to it. The only way around this would be to load additional credential sets within the script, and storing encryption files somewhere would be your best bet.

brscott

Would it be possible to break the script into 3 parts and put each part in a different component that could then have it's own credential? Keep in mind that there is no guarantee of the order the components run in.

An expansion of Thomas' idea. Since you can have stored credentials in encrypted files so that they are only useable by that user on that server. You add 2 more components that take the credential and store it as an encrypted file. the main script can load those files to get the extra credentials. The first time it runs the files might not exist, and each time you change the passwords, there would be one polling cycle where the password's were old, but other than that it would be correct. Basically you are "syncing" the passwords from the Solarwinds credential store to the local files.

SteveK

Maybe you could stage something wiht a local text file.

Component 1 does its thing, and when you want to branch, have it swap a value in a text file that Component 2

Component 2 is set with Credential 2. Its first step is to open the text file and look for its value to run. If its not, component exits out as up, if it is, continue with whatever step 2 is. Make sure you have something in step 2 to reset the value back. Then if that ties to component 3 do the same thing in a different text file (or could be the same)

Component 3 is basically a rinse repeat of 2.