Log In
Home
01/25/2021
Offline
Hello,
I have a questions regarding the amount of sessions that can be handled in a secureChannel, which I can’t figure out from the specification. Let’s assume I have a client-server system and my client app will be used by several users in parallel.
Does the client app need to create a new secureChannel
- Szenario 1: only once(to secure the connection between client and server)
- Szenario 2: for each user that needs data from the server (e.g., to better separate the sessions from each other)
What will be the correct architecture (according to the specification) or is this decision up to the application?
BR,
Tobias
P.S. The specification states (in part 4: Chapter 5.6.2.1 CreateSession Description) :
Before calling this Service, the Client shall create a SecureChannel with the OpenSecureChannel Service to ensure the Integrity of all Messages exchanged during a Session
This will be true for both scenarios, as both use a secureChanel that was created with OpenSecureChannel.
05/30/2017
Offline
The specification is silent on the number of sessions that can use the same SecureChannel however, alll UA TCP client implementations that I have looked at impose a restriction of one socket => one secure channel => one session.
The vagueness in the specification is there to handle other transports, such as HTTPS, where the SecureChannel implementation is outside of the scope of OPC UA.
1 Guest(s)
Usage Policy