This version introduces significant enhancements
🥇 CTT
- better support for certificate verification in Server to conform strictly to the OPCUA Specfication and make CTT security test pass/
🅰️ Aggregates
- [5a356fd] ClientSession#readAggreateValue has been added 👏 @shreeramk
- [69ebb4f] [052c67c] Minimum, Maximum and Average aggregate on server side
🐴 other
- [bea5412] for improve support for Variable containing ExtensionObjects (work in progress)
- [81778cf] provides decoded extension objects instead of opaque structure monitoredItem.on("change",)
(no need to use promoteOpaqueStructure inside DataChangeNotification in client MonitoredItem) - [15d08d7] improve handling of arrayDimensions in crawler
- [9b40b9a] export AccessLevel attribut to nodeset2.xml @DaniHaag
🐛 bug fixes
- [835759f] fix monitored item sample and object comparaison
- [b3bd8ae] do not send value change notification if sourceTimestamp has not changed
- [#785] fix TypeScript compiler Error exhibit by typescript 3.9 👏 @seang96
- [#786] Bugfixes in simple-client-ts.ts and simple-client.js] 👏 @pirminkager
- [#763] fix modeller readme 👏 @Mattross45
Notes:
- the complete Certificate chain is now verify up to the CA root cerficiate.
- a revocation verification is also perform,
- the enhancement in the certificate verification requires that the server is aware of the CA certificate of any connecting client that uses a Certificate emitted by this Certificate Authority.
- this means that the CA certificate must be installed in the issuers folder of the PKI and its associated Certificate Revocation List (CRL) installed in the corresponding CRL folder.
- Certificate verification will fail the connection if the CA certificate and its CRL doesn't preexist on the server.
- certificates file can now be updated ( added /removed) by an external file. a running node-opcua server will now periodically rescan the certificate list so there is no need anymore to stop and restart the server when certificates files changes.
👬 contributors