Closed RussellLeVasseur closed 3 years ago
Sorry if I closed last one too fast. I'm checking this right now.
Sorry. I missed to test -apiKey with powershell 5.1. Powershell core 7.1 was converting plaintext to secure.srting just fine. I'll add -force parameter that should fix this.
Well , this embarrassing bug is now fixed. Will release fix in few minutes.
@RussellLeVasseur I just published fix. It should be available at ps gallery in couple of minutes.
Please confirm fix and I close this later. And big thanks to you for reopened new issue so quickly.
@RussellLeVasseur I just published fix. It should be available at ps gallery in couple of minutes.
Thank you! I'll test on Tuesday after holiday weekend. I trust you've got it and closing now.
My previous issue was closed, but this is a very big breaking error....
Context
Won't connect to SnipeITPS with new Connect-SnipeitPS. When I revert back to 1.9.183 and go back to Set-SnipeitInfo, everything works again.
Your Environment
Expected Behavior
Connect to SnipeIT using a token string.
Current Behavior
Throws error when i pass the token as a string the same way I/we have always done.