Log In
Register
Forum
Topic RSS
18:19, EET
February 14, 2020
Offline
I am trying to establish a connection from the Siemens TIA controller CPU 1511-1 PN ( V 2.8.1) with the OPC UA client to my own OPC UA server (with Prosys SDK).
On the client side I get error 8020_0000: BadIdentityTokenInvalid, The user identity token is not valid.
Public boolean onValidate (Session session, ServerUserIdentity, userIdentity is not activated on my server.
OPC UA Server log have not a “Session activated”:
http://opcfoundation.org/UA/Se…..:4841/Test [[http://opcfoundation.org/UA/SecurityPolicy#None,None]]))): /192.168.101.35:56355 connected
11/26/2020 16:51:04.226 INFO [OPC-UA-Stack-Blocking-Work-Executor-34] com.prosysopc.ua.stack.transport.tcp.nio.OpcTcpServerSecureChannel – SecureChannel opened; SecurityToken(Id=1, secureChannelId=10, creationTime=26.11.2020 16:51:04, lifetime=3600000)
11/26/2020 16:51:04.232 INFO [OPC-UA-Stack-Blocking-Work-Executor-35] com.prosysopc.ua.server.SessionManager – Session created: OPC UA Verbindung_1 (ID=ns=1;g=b9c538ac-edb1-4f37-9982-425302c9cc1e Token=b=TZq1PKCEgt7nrQeXuLmS04hdF0S+7fNf0HLk9PXtt5I= Channel=(SecureChannelId=10 State=Open URL=opc.tcp://192.168.101.153:4841/Test SecurityPolicy=http://opcfoundation.org/UA/SecurityPolicy#None RemoteAddress=/192.168.101.35:56355))
11/26/2020 16:51:04.245 INFO [OPC-UA-Stack-Blocking-Work-Executor-37] com.prosysopc.ua.server.SessionManager – Session closed: OPC UA Verbindung_1 (ID=ns=1;g=b9c538ac-edb1-4f37-9982-425302c9cc1e Token=b=TZq1PKCEgt7nrQeXuLmS04hdF0S+7fNf0HLk9PXtt5I= Channel=(SecureChannelId=10 State=Open URL=opc.tcp://192.168.101.153:4841/Test SecurityPolicy=http://opcfoundation.org/UA/SecurityPolicy#None RemoteAddress=/192.168.101.35:56355))
11/26/2020 16:51:04.253 INFO [OPC-UA-Stack-Non-Blocking-Work-Executor-3] com.prosysopc.ua.stack.transport.tcp.nio.OpcTcpServerSecureChannel – Secure Channel closed, token=SecurityToken(Id=1, secureChannelId=10, creationTime=26.11.2020 16:51:04, lifetime=3600000)
11/26/2020 16:51:04.254 INFO [OPC-UA-Stack-Non-Blocking-Work-Executor-3] com.prosysopc.ua.stack.transport.endpoint.AbstractServerSecureChannel – Channel closed: Id=10
Siemens OPC UA client works with UaCPPServer. And my OPC UA server works with UaExpert.
My OPC UA server was written a long time ago and I have now updated it to the new SDK 4.4.2 without any changes.
Can you offer a solution to communication problems?
15:30, EET
Moderators
February 11, 2020
Offline
Hello,
Which version of the Prosys OPC UA SDK for Java were you using before updating to version 4.4.2?
Based on the log snippet, it looks like the Server isn’t receiving a request to activate the Session from the Client and thus the Server closes the Session.
If prossible, you could use Wireshark to capture traffic between the applications and look for CreateMonitoredItemRequests and CreateMonitoredItemResponses to see exactly how the Server (or Servers) assigns MonitoredItemIds. See https://www.prosysopc.com/blog/opc-ua-wireshark/ for instruction on how to capture OPC UA communication with Wireshark. If you’re running the applications on the same host, remember to select “Support loopback traffic” option when installing Wireshark.
You should look for ActivateSessionRequest in the Wireshark log to verify that the Client is attempting to activate the Session. You can also send the Wireshark logs to uajava-support@prosysopc.com so that we can take a look at them.
EDIT: Corrected typo on the version number.
15:24, EET
February 14, 2020
Offline
Hi,
thanks for your quick reply.
I can’t say exactly, but it can be version 3.0 – 3.1 of the Prosys OPC UA SDK for Java were we using before updating to version 4.4.2.
16:15, EET
Moderators
February 11, 2020
Offline
Hello,
The StatusCode Bad_IdentityTokenInvalid is returned for example when verifying SignatureData that is missing its algorithm and/or its signature. This check was added in version 4.4.0. Is your Client attempting to connect to the Server with non-empty and non-null userIdentityToken, or in other words non-anonymously, together with an empty or null userTokenSignature? This might have worked before, but it shouldn’t work anymore due to the added SignatureData verification check in newer versions of the SDK.
10:29, EET
February 14, 2020
Offline
Hello,
I have sent the Wireshark log file to uajava-support@prosysopc.com
Most Users Ever Online: 1919
Currently Online:
29 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 88
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 727
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1529
Posts: 6471
Newest Members:
kourtneyquisenbe, ellis87832073466, zkxwilliemae, gabriellabachus, Deakin, KTP25Zof, Wojciech Kubala, efrennowell431, wilfredostuart, caitlynfajardoModerators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1032, Jimmy Ni: 26, Matti Siponen: 349, Lusetti: 0
Administrators: admin: 1
