SDK Connection Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
SDK Connection Security
We are currently using the .NET SDK for thingworx.
out of a security perspective we are interested in which security-terms are part of the default SDK-Connection.
-Are there Certificates (Which Type/Class)
-Is there an internal VPN tunnel used
..
Where can we get such information?
At the moment we're asking the question if there is any security point we have to implement or wrap around the connection for our securitystandards, or if the Thingworx connections are safe enough.
Solved! Go to Solution.
- Labels:
-
Connectivity
-
Security
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thingworx SDK allows for SSL connection so HTTPS / WSS
You can also deploy a cert on the agent, that would have to map into Tomcat on the server side.
As far as tunneling, the way the agent works, it is sort of a 'reverse proxy' the agent locally can establish a TCP connection to whatever the device/system locally has access to and transfers the information of the established Web sockets connection. On the platform side, a client machine is presented an IP:Port to aim their client at.
Not sure if I'm interpreting your question properly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thingworx SDK allows for SSL connection so HTTPS / WSS
You can also deploy a cert on the agent, that would have to map into Tomcat on the server side.
As far as tunneling, the way the agent works, it is sort of a 'reverse proxy' the agent locally can establish a TCP connection to whatever the device/system locally has access to and transfers the information of the established Web sockets connection. On the platform side, a client machine is presented an IP:Port to aim their client at.
Not sure if I'm interpreting your question properly.
