You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@plc4x.apache.org by "iho-sar (via GitHub)" <gi...@apache.org> on 2026/07/09 08:24:42 UTC

Re: [I] [Bug]: Umati Sample Server BadIdentityTokenInvalid

iho-sar commented on issue #2154:
URL: https://github.com/apache/plc4x/issues/2154#issuecomment-4923105915

   Hello, I think I am seeing the same or a very similar problem here.
   
   I already tried a lot of different variants, but I still cannot connect to our Siemens SPS Simulation Server via PLC4X, while UaExpert works without issues.
   
   In my case:
   - OPC UA server security policy is set to `None`
   - authentication is done via `UserName`
   - PLC4X fails with `BadIdentityTokenInvalid (0x80200000)`
   
   From the PLC4X debug logs it looks like endpoint discovery, SecureChannel, and CreateSession work correctly, but `ActivateSession` fails.
   
   What looks suspicious in the logs is that PLC4X sends a `UserName` token with a policy like `UserName_Basic128Rsa15_Token`, and then the server rejects it with `BadIdentityTokenInvalid`.
   
   UaExpert can connect to the same server with the same credentials.
   
   So from my perspective this may not only be a special character issue, but possibly also a problem with how PLC4X selects or encodes the OPC UA `UserIdentityToken` for some servers, especially Siemens.
   
   If helpful, I can also share my debug logs.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@plc4x.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org