Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Issue connecting to the Simulation Server via HTTPs
March 15, 2019
15:46, EEST
Avatar
Dave62
Member
Members
Forum Posts: 4
Member Since:
March 15, 2019
sp_UserOfflineSmall 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

March 15, 2019
17:14, EEST
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 347
Member Since:
April 3, 2012
sp_UserOfflineSmall 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).

March 28, 2019
15:17, EEST
Avatar
Dave62
Member
Members
Forum Posts: 4
Member Since:
March 15, 2019
sp_UserOfflineSmall 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

March 28, 2019
16:51, EEST
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 347
Member Since:
April 3, 2012
sp_UserOfflineSmall 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.

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 78

Currently Online:
21 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 89

pramanj: 86

ibrahim: 68

kapsl: 57

gjevremovic: 49

TimK: 41

Fransua33: 39

fred: 36

Rainer Versteeg: 32

peterrob45: 25

Member Stats:

Guest Posters: 0

Members: 831

Moderators: 11

Admins: 1

Forum Stats:

Groups: 3

Forums: 14

Topics: 850

Posts: 3588

Newest Members:

stielerit, FonsCarver, THX, Automate, gamebaisunwin, reilev, brigettei47, olaloos025, leslieangles9, tomprodehl

Moderators: Jouni Aro: 824, Otso Palonen: 32, Tuomas Hiltunen: 5, janimakela: 0, Pyry: 1, Terho: 0, Petri: 0, Bjarne Boström: 347, Heikki Tahvanainen: 402, Jukka Asikainen: 1, Teppo Uimonen: 14

Administrators: admin: 0