Geo SCADA Expert SOAP authentication

[BevanWeiss]

Hi all,

This is the first time that I've really NEEDed to use the SOAP interface, and hence need to also use some form of authentication with it.

I'm able to connect and issue basic queries following this guide

https://community.se.com/t5/Geo-SCADA-Knowledge-Base/Using-SOAP-interface-to-connect-to-Geo-SCADA/ba...

However, this requires that 'Everyone' be given full read/browse permissions, and this won't fly in production.

I assume that with the SOAP interface it will be using some form of WS-Security, but based on previous experience with this, that can result in an awful lot of blind trial and error in configuring different options (i.e. does it want PasswordText, PasswordDigest, PasswordDigestExt, does it want encryption, does it need a Nonce, does it accept any ordering of these items, or must they be in a particular order, etc, etc, etc).

Annoyingly, if I supply Basic Authentication it appears to just ignore it, without raising a complaint telling me if it is wrong at all, but it just returns data as though the authentication failed.

@AdamWoodland  / @sbeadle  I'm hoping that either of you know the low level details.

I'm limited to javascript from an Android / iOS mobile device, so I really don't have a non-SOAP option.

[AdamWoodland · Accepted solution]

Not something I've dabbled in before, but looks like Steve has...

https://github.com/GeoSCADA/Node-Red-GeoSCADA/blob/master/GeoSCADA.js

Looks like some trickery going on with cookies.

[BevanWeiss]

That does indeed look like the answer.
I'm going to need to spend some time to digest this I reckon...

I suspect there may be some additional 'hidden' SOAP actions also (Invoke isn't declared in the WSDL).

But it looks like Invoke has a pretty 'wide' ability all the same, being able to call arbitrary methods on the COM interface it appears, by passing in the COM DispId.

xmlToSend += "<DispId>1398803523</DispId>\n";
...
xmlToSend += "<DispId>1129336836</DispId>\n";

Only going to be annoying trying to find what all the various DispIds are for the different interface methods.

And of course how to identify the appropriate Context (I'm not even sure what this Context 'means'.. like method vs put)

xmlToSend += "<Context>method</Context>\n";
...
xmlToSend += "<Context>put</Context>\n";