You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not know if it is intended or not. I get some difficulties making connection to OPC UA server. I use UserIdentityToken - Anonymous. After CreateSessionRequest, the CreateSessionResponse giving back that UserTokenPolicy-PolicyId: 0. But after that the ActivateSessionRequest using UserTokenPolicy - PolicyId: Anonymous, which in turn generate ServiceFault from the server.
Is it not common to use the CreateSessionResponse for the ActivateSessionRequest? In the code it is only using that if the UserTokenPolicy configuration nil.
I have also tested the server using dataFeed opc ua client and it is connected successfully.
Please advise if the server is not compliance with the standard OPC UA. Thank you in advance.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
I do not know if it is intended or not. I get some difficulties making connection to OPC UA server. I use UserIdentityToken - Anonymous. After CreateSessionRequest, the CreateSessionResponse giving back that UserTokenPolicy-PolicyId: 0. But after that the ActivateSessionRequest using UserTokenPolicy - PolicyId: Anonymous, which in turn generate ServiceFault from the server.
Is it not common to use the CreateSessionResponse for the ActivateSessionRequest? In the code it is only using that if the UserTokenPolicy configuration nil.
I have also tested the server using dataFeed opc ua client and it is connected successfully.
Please advise if the server is not compliance with the standard OPC UA. Thank you in advance.
Kind regards,
Januar
Beta Was this translation helpful? Give feedback.
All reactions