gavsto/AutomateAPI

Connect-ControlAPI command requires a ScreenConnect extension ID?

Opened this issue · 3 comments

crshovrd41 commented

I looked through a lot of the documentation but find no reference to anything about needing to have a ScreenConnect extension installed to make the connection. I looked through the code and can see that it is referencing CWCExtensionID, but when running Connect-ControlAPI, it doesn't ask for one.

I'm getting a 401 Unauthorized when attempting to connect. I tried another Control API from someone else and it doesn't reference an Extension ID, and it worked.

Is there something I'm missing?

Thanks in advance!

danrdj commented

@crshovrd41 were you able to get past the 401 Unauthorized issue and are you using the APIKey or credentials? I'm experiencing the same using the APIKey.

crshovrd41 commented
13ruce1337 commented

I've been digging into this for my org with the same issue and what I think is happening is there is no extension in the screen connect marketplace for this API. So you may need to write your own extension (C#) in ScreenConnect to respond to the AutomateAPI calls that are being sent. There is some documentation in screen connect on how to do this. I peaked into the extension made by another vendor for connection and it seems that's what they did. But made their extension publicly available on the screen connect extension marketplace.