Online Forums
Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.
Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.
Do not use the Contact page for technical issues.
OPC XML-DA Basic Authorization doesn't work
Best regards
Please Log in or Create an account to join the conversation.
Thanks a lot, now it works fine!
Best regards
Please Log in or Create an account to join the conversation.
please download the latest build of QuickOPC 2018.3 (should be 5.54.1133.1 or later) from our Web site or from Nuget, re-build your project and retest.
The basic authentication in OPC XML-DA should now work.
The principle is as follows:
- If there is a username (an optionally a password) in the URL, basic authentication will be used with this username and password.
- Otherwise, if (in the EndpointDescriptor) the NetworkSecurity.CustomNetworkCredential is 'true' (which is the default) and there is non-empty name in NetworkSecurity.NetworkCredential.UserName, basic authentication will be used with the user name and Password from the NetworkSecurity.NetworkCredential.
- Otherwise, no authentication will take place.
Thank you for reporting this issue.
Best regards
Please Log in or Create an account to join the conversation.
I'm using . NET Framework 4.6.2.
Please Log in or Create an account to join the conversation.
we are working on this.
Question: Are you using .NET Framework, or .NET Core? If you are using .NET Core, is it on Windows or on Linux?
Thank you
Please Log in or Create an account to join the conversation.
I have forwarded the issue(s) to the developer. I will let you know here when we know more.
My first impression is that the second approach (via URL) is meant to work, and we may have some bug there.
And, it is possible that we have currently no way to do the authentication through the request headers. But this is not the final answer, we will know more after investigating a little.
Best regards
Please Log in or Create an account to join the conversation.
We have an OPC XML DA server that requires authorization for writing values. Obviously, when I'm trying to write values without specifying username and password I'm getting error saying.
new ServerDescriptor("http://IP:port/DA") to new ServerDescriptor("http://IP:port/DA", new NetworkSecurity(user, password)). But, unfortunately it doesn't helped me.
Then I've compared using Wireshark requests sent from dOPC Explorer client and from my program and found that they are differ by Authorization request header. Requests sent from dOPC Explorer contains this header with specified username and password needed for Basic authorization while requests from my app doesn't contain such header at all.
Then I realized that NetworkSecurity might have nothing about HTTP authorization so I simply tried to specify user and password in URL like this:
http://username:password@IP:port/DA
And now I instead of access denied error I have another one saying
Here is the code:
Does basic HTTP authorization supported by the library? If yes - could you please correct me what I'm doing wrong.
Thanks in advance!
Please Log in or Create an account to join the conversation.