Can WinAPI be used via a Linux shell script?

[habskilla]

Or is WinAPI strickly a Powershell option?

[support]

Hi Habskilla,

 

Sorry, the WinAPI (Windows API) can only be called from Windows Machines using PowerShell. With the use of PowerShell, you can execute the script under the identity of an Active Directory account, which then gives you the same level of access as if you were logged into Passwordstate.

For Linux machines, you will need to use the standard API, which used API Keys for authentication.

Regards

Click Studios

[Sarge]

On 8/22/2018 at 7:06 AM, support said:

Sorry, the WinAPI (Windows API) can only be called from Windows Machines using PowerShell.

 

Possibly. But I wouldn't suggest it in a production environment yet.

Powershell Core is GA on Linux and MacOS.

 

https://blogs.msdn.microsoft.com/powershell/2018/01/10/powershell-core-6-0-generally-available-ga-and-supported/

[support]

Hi Guys,

 

Interesting - didn't know that was even in the works.
 

With PowerShell and our WinAPI, it is the parameter -UseDefaultCredentials which is used to pass the identity of the authenticated "Windows" account across to our API - basically it's impersonation. I'm not sure, but I don't think PowerShell Core can support this, as you're not logged on as a Windows User - unless there's a way to do this in Linux.

Regards

Click Studios

[Fabian Näf]

You can also save your credentials in a variable ($credVariabke = Get-Credentials) and pass this to the Invoke-Rest Powershell command. So I assume, there could be a way.

I also can imagine, that you could pass your credential to a REST-call header from another system (e.g. bash script) to authenticate, but I'm not familiar with bash scripts. 

[Azkabahn]

Hi,

 

i would not say that you can use WinApi only from windows machines. We are using WinApi from Linux machines for quite some time and it works fine  as simple as this:

curl  --ntlm  -u "user:pass" "https://passwordstate_url/winapi/passwords/XX"

 

[support]

Thanks for sharing

[habskilla]

Thanks very much.

 

Works without issue in our environment.

 

@Fabian Näf

What are you using to parse the json response?  Something like jq?

[Fabian Näf]

Hi Habskilla

 

To create the REST JSON Body I always go for the following approach: First create a PowerShell object and convert it then to a JSON-String. The big advantage of that is, that you don't have to care about any special characters, escaping and stuff like that.

$Body = @{
     FolderName = $Name
     Description = $Description
	 NestUnderFolderID = $ParentFolderID
	 APIKey = $global:PasswordStateSystemWideAPIKey
}
$jsonBody = $Body | ConvertTo-Json
$PasswordstateURLFull = "$($global:PasswordstateURL)/api/folders"
$result = Invoke-Restmethod -Method POST -Uri $PasswordstateURLFull -ContentType "application/json; charset=utf-8" -Body $jsonBody

The response I get is then stored in $result and can be accessed directly:

$output = $result.FolderID

If you have the answer as a string you also could use for the following approach:

$responseObject = $responseJsonString | ConvertFrom-Json

If you take a look the KeePassImport-Script you'll find some more examples.

 

All the best,

 

Fabian

[habskilla]

For those of you who are not keen of sending clear text passwords, I used gpg to encrypt the user:password.  I decrypt it on the fly with the following method:

curl -sS --ntlm -u $(gpg -qd --no-tty winapi.login.gpg) https://xxxx.com/winapi/passwords

[support]

Thanks for sharing habskilla - we appreciate it