Ignition to Tridium Server comms

I have trying to establish comms between Ignition and Tridium Server. It has been proven locally on an engineers laptop but the connection is faulted when using server to server comms. I have proven the IP path over the network and opened the relavent FW port to allow comms which our network team have seen. I have added the certificates into the correct place on the server. I keep getting this error message:
UaServiceFaultException: status=Bad_IdentityTokenRejected, message=The user identity token is valid but the server has rejected it.
at org.eclipse.milo.opcua.stack.client.UaStackClient.lambda$deliverResponse$5(UaStackClient.java:337)
at org.eclipse.milo.opcua.stack.core.util.ExecutionQueue$Task.run(ExecutionQueue.java:119)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

8.1.30 (b2023071408)
Azul Systems, Inc. 11.0.18

Can anyone help please. I`m new to using Ignition. Thanks

Ok, that probably means either:

  • you didn't provide a username/password, but the server expects one
  • you did provide a username/password, but it's either wrong or the server is not expecting one

Thank you Kevin

Did you get it fixed?

Hi Alec, No not yet but the port in the switch has stopped communicating so I`ve got to fix that first.

We had the same issue setting up the Tridium OPC server in a JACE 8000 to connect to Ignition. Turns out theres some bug (or maybe by design) where during set up you need to turn the server off, make your changes, save, then turn it back on. Once we found that out setting the server up was easy. May be the same issue for you, in our case none of the altered security settings were actually being utilized.

Fantastic i will try that . Thanks.

Which server did you turn off the Jace or the Ignition ?

Did your issues look like this ? Some points working and some not.

The Jace.