Invalid JSON primitive: . about snipeitps HOT 7 CLOSED

So, I'm guessing my question is silly, I asked it in the wrong place or SnipeITPS is dead. Let's hope it isn't dead.

from snipeitps.

Project undead, back from dead. And you question was not silly let's continue with it :)

@lcoppenr , could you provide more information about you powershell environment and command you tried to to run? are you using https and self signed certificates?

And if you are can use git , please try develop branch, if it fixed this. There's lots of changes that are waiting to be merged to master and from there powershell gallery.

from snipeitps.

If I am correct, running Get-Asset should just list all my assets. I've tried recreating the APIKey, but like I said it appears to be working with Postman to test the API remotely.

PS version: 5 1 19041 906

I have a script that runs on about 275 systems which updates/creates each computer asset. So there are a lot of systems with PS versions v3 to v7. Obviously <v5 doesn't work, but non of the systems are updating currently.

How do I install the development module within Powershell?

BTW: Thank you, thank you, thank you. Snipe-IT would be almost useless to me without this powershell module or a way to script computer asset updates and creates.

from snipeitps.

I wrote little guide how to install develop version
But before test it, please confirm that you are using https with trusted certificate. (postman down not complain by default, but now days powershell security has tightened up)
If it's self signed certificate you are using that could be source of problem. Look at #55 to find workaround for self signed certificates.

And thank you for thanks, you're welcome. This powershell module and nice snipeit api was main reason for me to start usin snipeit at start of this year.

from snipeitps.

I'm using a Let's Encrypt cert, which works fine from the web interface on a several computers (my management/test devices and several clients). I'll try the develop version and get back to you thx.

from snipeitps.

FIXED. You were right, it was a certificate problem on our cloud VM's firewall. Thank you for your time and thank you for keeping SnipeItPS alive. BTW: If there was a way to have SnipeItPS spit out an error like "can't connector site" or something that would be very helpful. Once I saw a JSON error, I felt a bit lost.

from snipeitps.

Great to heard that it fixed! We really need some error handling for webrequests.
Have fun with SnipeitPS!

from snipeitps.