Product: PowerShell Universal Version: 2026.1.3 Hi everyone, First of all, let me disclose tht I’m far from being an expert on PSU since I have only started working with it in a test environment recently, neither am I a professional programmer - I’m a hobbyist at best. I’ve been prototyping a PSU…

You could do it with subexpressions and the secret provider. Here is an older post that may help: [image] Secrets with "-" in the name PowerShell Universal Product: PowerShell Universal Version: 4.3.0 Hi, Quick question - we have several secrets with “-” in…

Thank you for your reply, do you have any specific pointers as to how to do it? I cannot seem to get it to work, I’ve tried the forms mentioned in the linked thread (and the link within as well) and tinkering with them but to no avail. For example if I attempt to use composed structures such as: $…

Try it like this: $SecretName = “name” Get-ChildItem -Path “Secret:$($SecretName)” edit: After checking again the subexpression is not needed. This works for me: Get-ChildItem -Path "Secret:$SecretName"

Okay, so your solution works and I realize that I’m being hindered by an underlying issue I had not detected sooner. For reference, here is my testing code: $tool = 'WebService' $site = 'SiteID' $SecretName = $tool+'_'+$site $user = 'UserName01' $passw = 'PassWord01!' $passw = ConvertTo-SecureStr…

(Edit: fake news, i take it back) Oh yeah, you can only create variables with New-PSUVariable, not secrets. So your script will probably work if you leave out the “Secret:” part.

Yesterday, I found that there is a PSU API for the Secrets. Maybe you will have more luck with it. [image] I ended up using the Secret Management module to dynamically save and retrieve secrets before I knew about the API.

Long sigh I see, thank you for your help and guidance I will look into that API thingy you mentionned.

I don’t mean to double-down or start a conversation, but isn’t it odd that the cmdlet New-PSUVariable allows you to create “Variables” that: Are marked as “Secret” in the creation output Take PSCredentials as InputObject Are hinted as being Secrets in the GUI Yet are not retrievable by the $Secre…

So, I had time to mess around a bit more and it turns out that if I create a Secret using: New-PSUVariable -Name $SecretName -Vault "Database" -Type "PSCredential" -InputObject $credsObject -Description "Test variable for secret creation via script" -Tag "Playwright" -TrustCertificate It “cannot b…

Huh, this is interesting. I can verify this behavior. The variable is only available in the $Secret: scope after it is edited in the UI. However, the secret is immediately available with. Get-PSUVariable -Name $SecretName Guess I came to the wrong conclusions about New-PSUVariable when I was try…

Retrieving Secrets by name when the name is a variable

PowerShell Universal

Dynamic March 19, 2026, 10:08am 2

You could do it with subexpressions and the secret provider.

Here is an older post that may help:

Topic		Replies	Views
Get-Variable with Secret variables in PSU 3 PowerShell Universal	4	828	March 17, 2023
Get-PSUVariable to get Secret PowerShell Universal	2	208	April 2, 2024
Secrets with "-" in the name PowerShell Universal	2	128	July 17, 2024
Clarification needed on variable references within scripts PowerShell Universal	5	155	April 3, 2024
Secret Variables blank	2	287	February 21, 2023

Retrieving Secrets by name when the name is a variable

Related topics