Bitwarden Powershell Issues

[djarbz]

I was excited to see this script pop up the other day.

I suggest adding this to the header of the script:

#Requires -Version 7.2

# To use PWSH v7
# Open File > Options > Advanced > Dynamic Folder
# Set the path to "%ProgramFiles%\PowerShell\7\pwsh.exe"

$PSStyle.OutputRendering = 'PlainText' was introduced in v7.2.

Also, I am unable to get past the check for the bw executable.

If I run the following in my terminal it works fine, but setting that path in the Custom Property field it will error out.

$path = "$env:ONEDRIVECONSUMER\AppSync\RoyalTS\bw.exe"

if (!(Test-Path -Path "$($path)" -PathType Leaf)) {
  Write-Error -Message "Bitwarden CLI utility not found at specified path. Please check CLI utility path in Custom Properties." -ErrorAction Stop
}

Further testing, I exported env: to a log file and it shows the correct values.

[GrinGrin]

Hi @djarbz ,

You're right, the OutputRendering is only in 7.2+ and that break usability with 5.1. As it is not a mandatory, I can either add a condition for the PowerShell version to include this only with 7.2+ or simply delete the line as the result seems not impacted if not present with 7.2+.

For the $env not resolved correctly it may be because of how the script get it:

$Bitwarden = ( New-Object PSObject |
  Add-Member -PassThru NoteProperty exec_path '$CustomProperty.BitWardenCLIExecutable$' |
  Add-Member -PassThru NoteProperty serverUrl '$CustomProperty.BitWardenServerURL$' |
  Add-Member -PassThru NoteProperty clientId '$CustomProperty.APIClientID$' |
  Add-Member -PassThru NoteProperty clientSecret '$CustomProperty.APIClientSecret$' |
  Add-Member -PassThru NoteProperty password '$CustomProperty.AccountPassword$' |
  Add-Member -PassThru NoteProperty session '' )

As I use RoyalTS Tokens replacement, I had to use single quotes to prevent PowerShell from attempting to expand $CustomProperty.xxx$ incorrectly.
Unfortunately this block variables expansion link $env that can be set in the property field. I'll try to find another way to evaluate the value set correctly before use.

I'll keep you tuned with update if I find a patch for those issues !

Best Regards,
Nicolas.

[djarbz]

Even if we could use/resolve the environment pre-token replacement such as variables are used in other fields.