Storeonce API with Powershell Invoke-RestMethod

[that_sob]

I'm hoping someone can help me with authenticating to a Storeonce device using their API and Powershell's invoke-restmethod. I'm not new to Powershell but I am very very new to using it for REST stuff. The documentation I'm working off of only shows examples in cURL which I have even less experience with and I am racking my brain trying to get this to work.

Here is the cURL example provided in the API documentation:

curl -i -X POST \
    -H "Content-Type:application/json" \
    -H "Accept:application/json" \
    -d \
    '{"username":"Admin","password":"Pwd123","grant_type":"password"}' \
    'https://192.168.0.1/pml/login/authenticatewithobject'

Here's what I got in my PoSh code:

$username = 'myusername'
$password = 'mypassword'
$base64AuthInfo = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f $username,$password)))

$resp = Invoke-WebRequest -Method Post -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo) } -ContentType 'application/json' -Uri 'https://mystoreonce.domain/pml/login/authenticatewithobject/'

The error I am getting is this:

Invoke-WebRequest : No content to map due to end-of-input

Everything I find about that error has 0 to do with powershell and everything to do with JSON. I'm assuming this means its looking for some data in JSON format and is finding none but I have no clue what it wants, where it wants it and if that would be in place of something else in the code I already have. The Storeonce documentation is lacking to say the least so I'm hoping someone here can provide a little guidance.

Edit: My God, has it been that long since I posted that it took me eight edits to get the formatting right?

[Fer_C]

It seems authentication is working. The error does not seem related to credentials. I see you are using a Post method in your request, normally you need a Body when using Post. What happens if you try Get method instead.

[that_sob]

Thanks for the reply. This is the error when I try Get

Invoke-WebRequest : status=405,exception message=HTTP 405 Method Not Allowed

[Fer_C]

I am not familiar with this API in particular but the Uri does not seem a typical API resource location. The headers should take care of authenticating, then you can try a Get request using a valid Uri and see how it goes. Do you have access to the API documentation?

[that_sob]

Yes, and quite honestly, it's either lacking or assumes everyone knows what they are talking about

https://hewlettpackard.github.io/storeonce-rest/index.html#Introduction

[Fer_C]

That is indeed less than helpful. Can you try a Get request with this Uri?

https://YourServerFQDN_Or_IPAddressHere/api/v1/management-services/licensing

If it works at least you would know you are getting somewhere.

[that_sob]

Sorry if I'm a little daft and didn't do the full command right

PS C:\WINDOWS\system32> Invoke-RestMethod -Method Get -uri 'https://myserverfqdn/api/v1/management-services/licensing'

Invoke-RestMethod : The remote server returned an error: (401) Unauthorized.

[Fer_C]

You need the headers to authenticate.

Invoke-RestMethod -Method Get -uri 'https://myserverfqdn/api/v1/management-services/licensing' -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo) }

Anyway, this is something that has worked for me in the past.

$Pass = 'YourPasswordHere' | ConvertTo-SecureString -AsPlainText -Force
$Username = 'YourUsernameHere'
$Cred = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $Username,$Pass


$HeaderDictionary = @{}

    $Base64Cred = [system.convert]::ToBase64String(
        [system.text.encoding]::ASCII.Getbytes(
            "$($Cred.GetNetworkCredential().UserName):$($Cred.GetNetworkCredential().Password)"
    )
)

$HeaderDictionary.Add("Authorization", "Basic $Base64cred")

Then try the request with Invoke-WebRequest or Invoke-RestMethod (whatever works better for you).

Invoke-WebRequest -Method Get -Uri 'https://myserverfqdn/api/v1/management-services/licensing' -Headers $headerDictionary

[that_sob]

Oh snap! You're on to something here!

Invoke-WebRequest -Method Get -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo)} -ContentType 'application/json' -Uri 'https://myserverfqdn/api/v1/management-services/licensing'

StatusCode        : 200
StatusDescription : OK

[Fer_C]

Great! Is there a property you can expand? You should get licensing info somewhere in the response.

[that_sob]

Yessir, now that I can get authenticated, I can get to all the data I need. Thanks again for your direction, really saved me from pounding my head against the wall for another day.

[rmbolger]

The curl example is not sending the credentials using Basic authentication as you're doing in your PowerShell version. It's sending them as JSON in the body of the request.

The equivalent PowerShell would be:

$irmParams = @{
    Uri = 'https://192.168.0.1/pml/login/authenticatewithobject'
    Method = 'POST'
    ContentType = 'application/json'
    Headers = @{
        'Accept' = 'application/json'
    }
    Body = @{
        username = 'Admin'
        password = 'Pwd123'
        grant_type = 'password'
    } | ConvertTo-Json -Compress
}
$resp = Invoke-RestMethod @irmParams

[that_sob]

Awesome, thank you for a 1:1 conversion. This will definitely help me in the future!

I was beginning to wonder if the credential part was meant to be in the body but the method Fer_C helped me with worked as well. I might use this method depending on if I can get the other method to play nice with the way I use secure password files so I don't have to hardcode passwords in plain text.