Log In
Home
10/09/2017
Offline
How can I make the standard LDS from OPC Foundation to provide discovery over HTTPS? I have opcualds.exe installed, and it does not do it by default (I expect it to be listening at port 4843, is that right?). Perhaps through a configuration file - but there is none alongside the EXE. Can anybody help?
05/30/2017
Offline
The current LDS does not support HTTPS.
Please add a feature request to GitHub:
https://github.com/OPCFoundati.....LDS/issues
Please talk a bit about your use case and why HTTPS is your preferred transport.
10/09/2017
Offline
Thank you. I actually do not necessarily need LDS to support HTTPS. I am developing a client that should be generically usable, and wanted to test the discovery over HTTPs, so I thought that the standard LDS could possibly help me.
Maybe I was too concerned about this case. If it's not used by anybody, then I probably just should not care. My feeling was that pretty much everything is now being moved from HTTP to HTTPS, therefore I thought it was relevant.
05/30/2017
Offline
With OPC UA, TCP is the preferred mode of communication for the vast majority of applications. When HTTPS is used it will be for some external gateway where an LDS does not really make sense (i.e. traffic will be connect directly to the UA server instead going through an ad-hoc discovery process).
1 Guest(s)
Usage Policy