feat(binding-opcua): Add channel security support #1401

[erossignon]

Implements OPC UA channel security by allowing the configuration of security mode and policy and authentication

This change introduces a certificate manager to handle client-side certificates.

Key changes:

• Added new SecurityScheme

     OPCUASecureSecuritySchemeBase (abstract)
         -> OPCUAChannelSecurityScheme
	       -> OPCUAUnsecureChannelScheme
	       -> OPCUASecureSecurityScheme
	 -> OPCUASecureSecurityScheme 
               -> OPCUACertificateAuthenticationScheme 
               -> OPCUAUserNameAuthenticationScheme

• Implemented a shared OPCUACertificateManager for PKI.

  PKI folder for OPCUAPrococolClient is set to env-path("binding-opcua-wot").PKI

  which resolve to
  on window:
  C:\Users<User>\AppData\Roaming\binding-opcua-node-wot\Config\PKI
  on linux:
  ~/.config/binding-opcua-node-wot/PKI on linux'
  on macOs:
  ~/Library/Application Support/binding-opcua-node-wot/PKI

• Added tests for secure communication.

[erossignon]

Waiting for #1417 to be completed

[relu91]

PR looks good, but I have these two questions/suggestions:

• ClientManager logic can be factored out in a single ts file/class
• Are we all ok to expose and add OPCUA specific typings and test to the core package (which should be agnostic from the underlying protocol)?

[danielpeintner]

• Are we all ok to expose and add OPCUA specific typings and test to the core package (which should be agnostic from the underlying protocol)?

Ideally, we should not do that.
I wonder whether we can create a generic placeholder which each security scheme could use...

[erossignon]

• Are we all ok to expose and add OPCUA specific typings and test to the core package (which should be agnostic from the underlying protocol)?

@relu91, Can you clarify what you have in mind ?

[relu91]

two things:

• Move the new declarations about security schemes to opcua package
• Make the tests about the combo scheme generic. In the sense that I don't think there is a need to use specific OPC UA security bindings to test the new logic introduced in the core (or do I miss something?).

p.s. I noticed that SecurityType is not used anywhere in our codebase I'd deprecate it and remove it in 1.0.0 @danielpeintner

[danielpeintner]

p.s. I noticed that SecurityType is not used anywhere in our codebase I'd deprecate it and remove it in 1.0.0 @danielpeintner

👍 Makes sense
Created #1419

[erossignon]

Created #1419

I can take it while I am here.

[danielpeintner]

LGTM

[relu91]

Maybe I'm wrong, but I think you missed this:

ClientManager logic can be factored out in a single ts file/class

[erossignon]

Maybe I'm wrong, but I think you missed this:

ClientManager logic can be factored out in a single ts file/class

@relu91 Sorry Can you be more specific ?

update:

I guess, by extrapolating the meaning of "ClientManager" that you wan't the singleton management for the OPCACertificateManager to be factored out of the OpcuaProtocolClient class.
I'll do this.

I'll also move the resolution of WotSecurity=>OPCUASecurity to a dedicated file.

Let me know if there are more you had in mind.

[relu91]

Yes, that's what I had in mind, thank you.

[relu91]

Ah, now I noticed a little bit of inconsistency in the file naming scheme, sometimes using _ sometime - . We can fix it later with a refector PR.