Could not instantiate the SecurityPolicy for the UserToken when try connect username/password #2747
Comments
|
"Could not create SecurityContext" is not very detailed.
|
|
the same situation when using UA_Client_connect_username() with username/password. do you resovle this problem ? |
|
Sorry, Unfortunately no yet. Thanks
…Sent from my iPhone
On May 24, 2019, at 5:02 AM, fanucwj ***@***.***> wrote:
the same situation when using UA_Client_connect_username() with username/password. do you resovle this problem ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
i only make use UA_Client_connect_username(client, "opc.tcp://190.1.1.2:412",name,secret),but can not connect to server. use open62541.c/h , sometimes i thought whether the library is well,and you? |
|
and i think it is very basic to use this fanuction ,but still not work. make me crayz |
|
Sorry, Unfortunately no yet. Thanks
|
|
I think in some part of library very deep inside the token (user name and password) is creating but not encrypted, that is the problem, so when server reject the security token
Thanks
…Sent from my iPhone
On May 24, 2019, at 1:01 PM, fanucwj ***@***.***> wrote:
and i think it is very basic to use this fanuction ,but still not work. make me crayz
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
A couple of weeks, but seems it is not possible with current library version, doesn’t support it yet.
…Sent from my iPhone
On May 24, 2019, at 1:17 PM, fanucwj ***@***.***> wrote:
hi.glad to see u. how long have u debug for this?------------------ 原始邮件 ------------------
发件人: ***@***.***>
发送时间: 2019年5月25日(星期六) 凌晨0:49
收件人: ***@***.***>;
抄送: ***@***.******@***.***>;
主题: Re: [open62541/open62541] Could not instantiate the SecurityPolicyfor the UserToken when try connect username/password (#2747)
Sorry, Unfortunately no yet. Thanks
Sent from my iPhone
> On May 24, 2019, at 5:02 AM, fanucwj ***@***.***> wrote:
>
> the same situation when using UA_Client_connect_username() with username/password. do you resovle this problem ?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
how do u config the client? and i only use username/password without certify
|
|
do u mind to exchange wechat for convenient? where u?
|
|
hello |
|
Hello
I don’t mind, please what is your contact info to send you invitation. We are in USA.
Also quick questions:
1-do you have possible solution for encrypted username/password, as individual support service? It is very important for us.
2- also we are trying with certificate/private key but facing other challenges.
In general we would like to know if you offer priority support service?
Thanks
…Sent from my iPhone
On May 24, 2019, at 11:13 PM, fanucwj ***@***.***> wrote:
hello
this is my siample demo #2762
is it like this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
hello, i am new to study opcua and will do hard research at this project. i would like to exchange experience on this thanks for all |
|
Did you already have a look at the examples here: First try to understand the example code and what is happening there. Then adapt that code to use it with a Kepware Server & Co. Especially try to use your own certificates and make sure that the example code is working for you. Then adapt it. See also #934 |
|
i have already solved this problem successfully,referring to examples |
|
You're welcome |
|
This pull request #2804 will resolve the issue. |
Hi, thank you so much for sharing this amazing work you guys are doing and supporting.
I am facing since some weeks same problem trying to connect to Kepware V6 using username & password with security police #None. I can connect if no username/password is used. I read multiple issues related, and based on recommendation I tried to include the supported security policies manually but with no success after multiple back and for. I got message 'Could not create securityContext', I am using the ca.crt and ca.key generated by the self-signed tool provided. Attached is section of code in C++ and screenshot. Please could you recommend where to looks, or the proper way to complete the token properties to allow get connection
connect_username_password_kepware.txt
Thank you so much for any info
UA_LOGLEVELset as low as necessary) attachedThe text was updated successfully, but these errors were encountered: