Log In
Register
Forum
Topic RSS
7:13, EET
March 22, 2018
Offline
Hi,
We have downloaded latest OPC UA Source code on 21st March 2018, after compiling and executing OPC UA Sample Client and tries to communicate with OPC UA Sample Simulation Server (distributed by ProSys). We found below error while opening session,
Error: “Endpoint does not supported the user identity provided”.
We are using OPC UA Server (distributed by ProSys),
https://www.prosysopc.com/products/opc-ua-simulation-server/
However, we created one user in ProSys OPC UA Simulation Server, and we are using the same user authentication for communication with OPC UA Client over https endpoints.
Do we need to configure ProSys UA Server more to execute with OPC UA Sample Client over https endpoints?
How to test ProSys OPC UA Simulation Server for other OPC UA Clients?
If you need further information, please reply back.
Regards,
Rahul
14:48, EET
April 17, 2013
Offline
Hi,
It sounds like the server is not accepting user identity tokens. So, check that the “Username&Password” checkbox is checked in User Authentication Methods. And also make sure that the setting is taken into use by restarting the Prosys OPC UA Simulation Server.
Other than that, please paste the actual stack trace of the error and we’ll be happy to provide more advice.
14:19, EET
March 22, 2018
Offline
1. Checked the “Username&Password” checkbox is checked in User Authentication Methods, and restarted Prosys OPC UA Simulation Server.
–> Still its giving same error
2. Regarding stack trace, I can not paste images here, I have added the same issue on Git support for OPC UA Foundation as,
https://github.com/OPCFoundation/UA-.NETStandard/issues/411
On this link you may find exact stack trace by clicking on image
15:18, EET
April 17, 2013
Offline
Hi,
Thanks for the information. According to my understanding, the issue is probably caused by the client application. So, it’s good that you have reported the issue to the Github repository.
If I understood correctly, you have already validated that the connection works with our Prosys OPC UA Client. If not, please fill the download form at our website (https://prosysopc.com/products/opc-ua-client/evaluate/) and validate that the connection works with this client application.
All this being said, I’d also like to mention that https communication is not widely used in OPC UA applications. The opc.tcp communication is much more widely used.
15:24, EET
April 17, 2013
Offline
Actually, please ignore my last message.
Looking more closely to the picture that you have posted to Github, the client application tries to connect to
This is the opc.tcp endpoint. This endpoint will not accept https connections.
Instead, you need to connect to the https endpoint in port number 51443.
13:07, EET
September 24, 2019
Offline
Hi,
I am trying to connect the prosys OPC UA server to prosys OPC UA client on the same machine.
When I try to connect both via UA TCP address client is getting connected, but when I try the same using UA HTTPS is “Cannot discover server application from…”.
Can you please help me with the problem?
Most Users Ever Online: 1919
Currently Online:
20 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: 735
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1521
Posts: 6442
Newest Members:
AnnelCib, dalenegettinger, howardkennerley, Thomassnism, biancacraft16, edgardo3518, JessevGool, briannestevenson, aracelymassina, wotikaModerators: Jouni Aro: 1025, Pyry: 1, Petri: 0, Bjarne Boström: 1024, Jimmy Ni: 26, Matti Siponen: 346, Lusetti: 0
Administrators: admin: 1
