-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in twin service when using x509 authentication #121
Comments
Hi @mm-dlwe, can you provide more info around the server you are trying to access. Also, an example request json with a sample user name password so I can build a test around it? The access denied appears to point to an issue with how the credential is passed to the server. Assuming the password is correct. |
Sure the server is the UACppServer Demo from Unified automation configured to accept authentication using X509 Certificates. I use this request for publishing a node in the twin server API:
I put the test certificate in here as well so that yout can test with it (its a base64 encoded pfx). Wheter I use header.elevation or not does not matter. The authentication data was set using update enpoint information as well to get thje endpoint activation working. The certificate is correctly whitelisted in the UaCPPServer and connections using UaExpert with the same certificate are working. For user name password test we use the codesys opcua server of a WAGO PFC200. Which is a bit strange because it requires username and password to be send unencrypted. |
Capability to use certificates for user auth in OPC Publisher 2.9* will be tracked in #2005. |
Describe the bug
When using authentication data in combination authentication all operations return 401 Unauthorized. This happens with "UserName" as well as with "X509Certificate".
The twin module connects to the server and passes the auth data. the session is established. On executing a command the connection changes from Ready to Error:
A wrong password shows a different error as expected:
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: