Node opcua 2.2.0 version: Cannot find ANONYMOUS user token policy in end point description #693

samminen · 2019-11-04T20:26:47Z

I'm submitting a ... (check one with "x")

Current behavior

(node:3748) UnhandledPromiseRejectionWarning: Error: Cannot find ANONYMOUS user token policy in end point description
    at createAnonymousIdentityToken (C:\Edge\Solution\edge\rig-connectors\opc-ua-client-service\src\node_modules\node-opcua-client\source\private\opcua_client_impl.ts:135:15)
    at OPCUAClientImpl.createUserIdentityToken (C:\Edge\Solution\edge\rig-connectors\opc-ua-client-service\src\node_modules\node-opcua-client\source\private\opcua_client_impl.ts:1253:41)
    at OPCUAClientImpl._activateSession (C:\Edge\Solution\edge\rig-connectors\opc-ua-client-service\src\node_modules\node-opcua-client\source\private\opcua_client_impl.ts:945:14)
    at _createSession (C:\Edge\Solution\edge\rig-connectors\opc-ua-client-service\src\node_modules\node-opcua-client\source\private\opcua_client_impl.ts:429:22)
    at ClientSecureChannelLayer.performMessageTransaction (C:\Edge\Solution\edge\rig-connectors\opc-ua-client-service\src\node_modules\node-opcua-client\source\private\opcua_client_impl.ts:904:13)
    at modified_callback (C:\Edge\Solution\edge\rig-connectors\opc-ua-client-service\src\node_modules\node-opcua-secure-channel\source\client\client_secure_channel_layer.ts:1292:31)
    at process_request_callback (C:\Edge\Solution\edge\rig-connectors\opc-ua-client-service\src\node_modules\node-opcua-secure-channel\source\client\client_secure_channel_layer.ts:137:5)
    at ClientSecureChannelLayer._on_message_received (C:\Edge\Solution\edge\rig-connectors\opc-ua-client-service\src\node_modules\node-opcua-secure-channel\source\client\client_secure_channel_layer.ts:745:9)
    at MessageBuilder.ClientSecureChannelLayer.messageBuilder.on (C:\Edge\Solution\edge\rig-connectors\opc-ua-client-service\src\node_modules\node-opcua-secure-channel\source\client\client_secure_channel_layer.ts:387:22)
    at MessageBuilder.emit (events.js:182:13)
warning.js:18
(node:3748) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
warning.js:18
(node:3748) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Expected behavior
When I create subscriptions using Node Opcua 2.2.0 version, I see above "Cannot find ANONYMOUS user token policy in end point description" issue.

Minimal reproduction of the problem with instructions

private  userIdentity: NodeOPCUA.UserIdentityInfo /*NodeOPCUA.UserIdentityInfoUserName*/ = {type:   NodeOPCUA.UserTokenType.UserName | 
            NodeOPCUA.UserTokenType.Anonymous |
             NodeOPCUA.UserTokenType.Certificate, 
              userName:"", password:""};

this.userIdentity =  {
  type: NodeOPCUA.UserTokenType.UserName,
  userName: this.userName,
  password: subDecryptedPassrdStr
};

I have Node opcus server 2.x version with basic nodes created and updating with random values__
In OPCUA client (2.2.0) I created monitor item for the node-id and after some time, I see above exception/warning_______

...

gist:

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

( ) my request is related to node-opcua acting as a OPCUA CLIENT
( ) my request is related to node-opcua acting as a OPCUA SERVER
( ) I have installed node-opcua from source ( using git clone)
( ) I have installed node-opcua as a package ( using npm install )
( ) I am using an application that uses node-opcua
- ( ) node-red
- ( ) other : please specify
Device: _____
OS version: _WIN10
- ( ) Windows : version : _________
- ( ) Linux : version : _________
- ( ) MacOs : version : _________
- ( ) Raspbian: version : _________
- ( ) Other : specify :
Description of the other OPCUA system I am trying to connect to:
- Name:_________
- Version:_________
- Manufacturer/Software vendor:_________
- link : https://
node-opcua version: :

Node:
node --version =2.2.0

The text was updated successfully, but these errors were encountered:

samminen · 2019-11-05T13:14:01Z

Is there a sample program where UserIdentity ( AnonymousIdentity | UserIdentityInfoX509 | UserIdentityInfoUserName) options implemented ?

erossignon · 2019-11-09T16:56:50Z

@samminen Please provide a complete ts script in a gist that reproduces the issue.

rafaturtle · 2020-02-24T06:20:55Z

Hi. I'm having the same issue, using the simple client tutorial againsta a Kepware V6 server on a different server. Firewall is open and I've configured the endpoint to accept security None. It fails when creating the session.
Gist: 68adbd8b5e280d87dcd7045ed07d3cef

youngkzy · 2020-05-20T18:18:45Z

Found a similar issue when using "node-red-contrib-opcua" breaks when it was upgraded to use node-opcua 2.4.4. We had to downgrade to use version prior to that node-opcua version, Kepware connects fine using anonymous security None. Have not tested security levels yet on newer versions. Usually "No Security" is chosen to first get connection for remote clients. This busted while also using LOCAL Kepware Server.

erossignon · 2020-05-27T18:35:45Z

Can you please run this gist to extract the endpoints exposed by your server
https://gist.github.com/erossignon/5b2a5ff9edf7abd72d604414def13c2b
for example:

ts-node get_endpoints -e opc.tcp//opcuademo.sterfive.com:26543

This will output the exposed endpoints of your server such as

ndpoint                                Application URI                              Product URI       Application Name  securityLevel  Security Mode   securityPolicyUri                                          Type    certificate  discoveryUrls
--------------------------------------  -------------------------------------------  ----------------  ----------------  -------------  --------------  ---------------------------------------------------------  ------  -----------  -------------
opc.tcp://opcuademo.sterfive.com:26543  urn:opcuademo.sterfive.com:NodeOPCUA-Server  NodeOPCUA-Server  NodeOPCUA         3              None            http://opcfoundation.org/UA/SecurityPolicy#None            Server  ...
opc.tcp://opcuademo.sterfive.com:26543  urn:opcuademo.sterfive.com:NodeOPCUA-Server  NodeOPCUA-Server  NodeOPCUA         10              Sign            http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15   Server  ...
opc.tcp://opcuademo.sterfive.com:26543  urn:opcuademo.sterfive.com:NodeOPCUA-Server  NodeOPCUA-Server  NodeOPCUA         15              Sign            http://opcfoundation.org/UA/SecurityPolicy#Basic256        Server  ...
opc.tcp://opcuademo.sterfive.com:26543  urn:opcuademo.sterfive.com:NodeOPCUA-Server  NodeOPCUA-Server  NodeOPCUA         20              Sign            http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256  Server  ...
opc.tcp://opcuademo.sterfive.com:26543  urn:opcuademo.sterfive.com:NodeOPCUA-Server  NodeOPCUA-Server  NodeOPCUA         30              SignAndEncrypt  http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15   Server  ...
opc.tcp://opcuademo.sterfive.com:26543  urn:opcuademo.sterfive.com:NodeOPCUA-Server  NodeOPCUA-Server  NodeOPCUA         35              SignAndEncrypt  http://opcfoundation.org/UA/SecurityPolicy#Basic256        Server  ...
opc.tcp://opcuademo.sterfive.com:26543  urn:opcuademo.sterfive.com:NodeOPCUA-Server  NodeOPCUA-Server  NodeOPCUA         50              SignAndEncrypt  http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256  Server  ...

Identify Token for : Security Mode= None  Policy= http://opcfoundation.org/UA/SecurityPolicy#None
policyId                    tokenType  issuedTokenType  issuerEndpointUrl  securityPolicyUri
--------------------------  ---------  ---------------  -----------------  ---------------------------------------------------------
username_basic256           1          null             null               http://opcfoundation.org/UA/SecurityPolicy#Basic256
username_basic128           1          null             null               http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15
username_basic256Sha256     1          null             null               http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256
certificate_basic256Sha256  2          null             null               http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256
certificate_basic256        1          null             null               http://opcfoundation.org/UA/SecurityPolicy#Basic256
certificate_basic128        1          null             null               http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15
certificate_basic256Sha256  1          null             null               http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256
certificate_basic256Sha256  2          null             null               http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256
anonymous                   0          null             null               null

Identify Token for : Security Mode= Sign  Policy= http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15
policyId          tokenType  issuedTokenType  issuerEndpointUrl  securityPolicyUri
----------------  ---------  ---------------  -----------------  -----------------
usernamePassword  1          null             null               null
certificateX509   2          null             null               null
anonymous         0          null             null               null

Identify Token for : Security Mode= Sign  Policy= http://opcfoundation.org/UA/SecurityPolicy#Basic256
policyId          tokenType  issuedTokenType  issuerEndpointUrl  securityPolicyUri
----------------  ---------  ---------------  -----------------  -----------------
usernamePassword  1          null             null               null
certificateX509   2          null             null               null
anonymous         0          null             null               null

Identify Token for : Security Mode= Sign  Policy= http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256
policyId          tokenType  issuedTokenType  issuerEndpointUrl  securityPolicyUri
----------------  ---------  ---------------  -----------------  -----------------
usernamePassword  1          null             null               null
certificateX509   2          null             null               null
anonymous         0          null             null               null

Identify Token for : Security Mode= SignAndEncrypt  Policy= http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15
policyId          tokenType  issuedTokenType  issuerEndpointUrl  securityPolicyUri
----------------  ---------  ---------------  -----------------  -----------------
usernamePassword  1          null             null               null
certificateX509   2          null             null               null
anonymous         0          null             null               null

Identify Token for : Security Mode= SignAndEncrypt  Policy= http://opcfoundation.org/UA/SecurityPolicy#Basic256
policyId          tokenType  issuedTokenType  issuerEndpointUrl  securityPolicyUri
----------------  ---------  ---------------  -----------------  -----------------
usernamePassword  1          null             null               null
certificateX509   2          null             null               null
anonymous         0          null             null               null

Identify Token for : Security Mode= SignAndEncrypt  Policy= http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256
policyId          tokenType  issuedTokenType  issuerEndpointUrl  securityPolicyUri
----------------  ---------  ---------------  -----------------  -----------------
usernamePassword  1          null             null               null
certificateX509   2          null             null               null
anonymous         0          null             null               null

What is the result on your side ?

erossignon · 2020-05-30T09:30:37Z

@rafaturtle @youngkzy For reference Kepware may prevent unsecure connection and in this situation the client mus use secure connection and its certificate must be trusted on Kepware side. Mika explained it very well in mikakaraila/node-red-contrib-opcua#151.

@samminen , please provide additional information to help us understand your specific problem ?

erossignon · 2021-04-24T17:43:27Z

@samminen I think that this problem has faded away on your side . Let closed,

ashok0617 · 2021-10-07T03:47:54Z

@samminen I think that this problem has faded away on your side . Let closed,

This issue appeared for me recently with KEPServerEX v6.10 and thought might be useful to share here. I added issue details with expected fix on server side. This is not node issue.

mikakaraila/node-red-contrib-opcua#151

marutimuthu · 2023-10-23T19:31:28Z

This error is due to anonymous login being disabled by default in Kepserver.

To allow anonymous login: Edit -> Properties -> OPC UA -> Allow Anonymous Login -> Yes

I was facing the same issue and it was resolved after anonymous login was enabled.

erossignon added the need more info The issue cannot be resolved as described and need deeper investigation label Nov 9, 2019

This was referenced Oct 13, 2020

Version 0.2.83 invalid endpoint mikakaraila/node-red-contrib-opcua#202

Closed

Unable to connect to Kaiser-Raman mikakaraila/node-red-contrib-opcua#199

Closed

issue is still unresolved. mikakaraila/node-red-contrib-opcua#197

Closed

erossignon closed this as completed Apr 24, 2021

guenhter mentioned this issue Jun 16, 2023

Cannot find ANONYMOUS user token policy in end point description node-opcua/opcua-commander#39

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Node opcua 2.2.0 version: Cannot find ANONYMOUS user token policy in end point description #693

Node opcua 2.2.0 version: Cannot find ANONYMOUS user token policy in end point description #693

samminen commented Nov 4, 2019 •

edited by erossignon

samminen commented Nov 5, 2019

erossignon commented Nov 9, 2019

rafaturtle commented Feb 24, 2020 •

edited by erossignon

youngkzy commented May 20, 2020 •

edited

erossignon commented May 27, 2020 •

edited

erossignon commented May 30, 2020

erossignon commented Apr 24, 2021

ashok0617 commented Oct 7, 2021

marutimuthu commented Oct 23, 2023 •

edited

Node opcua 2.2.0 version: Cannot find ANONYMOUS user token policy in end point description #693

Node opcua 2.2.0 version: Cannot find ANONYMOUS user token policy in end point description #693

Comments

samminen commented Nov 4, 2019 • edited by erossignon

samminen commented Nov 5, 2019

erossignon commented Nov 9, 2019

rafaturtle commented Feb 24, 2020 • edited by erossignon

youngkzy commented May 20, 2020 • edited

erossignon commented May 27, 2020 • edited

erossignon commented May 30, 2020

erossignon commented Apr 24, 2021

ashok0617 commented Oct 7, 2021

marutimuthu commented Oct 23, 2023 • edited

samminen commented Nov 4, 2019 •

edited by erossignon

rafaturtle commented Feb 24, 2020 •

edited by erossignon

youngkzy commented May 20, 2020 •

edited

erossignon commented May 27, 2020 •

edited

marutimuthu commented Oct 23, 2023 •

edited