Log In
Register
Forum
Topic RSS
15:46, EET
March 15, 2019
Offline
Hi all,
for some reason I am unable to reach the Simulation Server via HTTPs web browser. Even after explicitly trusting my client certificate from the “Certificates” tab in the server conf tab, I get a connection closed error message after putting the default HTTPs endpoint; same also after importing the certificate in my browser trusted store, regardless of the browser (firefox, IE, chrome).
Any idea why this is failing? Or is just that this HTTPs communication is made for between the Server and any Client, not for any web-based browsing usage?
Thanks in advance,
David
17:14, EET
April 3, 2012
Offline
Hi,
“HTTPS” in the context of OPC UA has nothing to do with the “real, web” HTTPS. In UA HTTPS is only used as an alternative secure channel “low-level-implementation” for transmitting binary-encoded OPC UA messages instead of the opc.tcp protocol. It can be only used with an OPC UA Client specifically made to use it.
P.S. Additionally even when tried to use via specific OPC UA Client, it usually is very hard to get it to work, as almost no-one supports that in practice at all or correctly (including us at the moment, version 4.0.0 of our SDK should fix main issues soon), and it has also received some changes in UA 1.04 version (which the SDK 4.0.0 also supports), there it specifically mentions that it should be “opc.https” and not just “https” (this confusion might be one reason). In practice opc.tcp should be used always and only if that is not possible, then https could maybe be an option (e.g. some very strict firewall could be a cause, which is probably the reason it was added in the first place to the specification).
15:17, EET
March 15, 2019
Offline
Thank you Bjarne, this clarifies. Is there any plan though to also expose the Server as a real web HTTPs client in the future product roadmap (on top of existing mobile and other clients) so that it could be managed from a same central interface than other apps?
David
16:51, EET
April 3, 2012
Offline
Hi,
It is not currently planned, but we have sometimes had discussions about that so maybe some day. The current approach is also a bit more maintainable than supporting all possible browsers.
1 Guest(s)
