Adds a complex type system client library extension for custom enumerations and structure types based on a server dictionary or DataTypeDefinition using emitted classes at runtime.
- Custom types are added to the session factory, not to the global factory. Types are loaded when the session connects by adding
` var complexTypeSystem = new ComplexTypeSystem(session);
await complexTypeSystem.Load();
`
- Custom type properties can be accessed with an accessor [propertyname] or [index]. Direct access through the properties is possible, but some cases do not update the optional or union flags correctly.
- Support includes V1.03 dictionaries and V1.04 DataTypeDefinitions (--> known issues).
- NetCoreComplexClient can be used for quick testing servers. It prints out all custom types with content and subscribes to all. Also includes sample how to write back complex type variables and how to output JSON.
- The UA Sample Client and the Quickstart Data Type client can be used for testing with UI. Many issues were adressed to be able to read and write complex types, however some support is limited, e.g. only editing simple fields is currently working (help wanted).
- Caveat: The complex type libaries for .Net Core must be built for .netcoreapp, so it needs a seperate nuget package for the complex type client extension.
- Support for a factory type builder class to allow to plugin other type builder methods (e.g. Codedom etc...)
- Added JSON test case and include the complex types client in the testing shell script, so the complex types lib is tested on mac/linux too.
- Few fixes in the JSON encoder.
Finding enough servers with custom types is an issue, so if you find servers with unsupported custom types please provide feedback.
Known limitations:
- Only V1.03 OPC binary dictionaries are supported (no XML Schema dictionaries).
- V1.03 dictionary structure definitions are only supported if they can be mapped to a V1.04 DataTypeDefinition. Nested types and cross dictionary refs should work.
- OptionSet is only partially implemented. Only shows the byte arrays, not the flags.
- Opaque Types in dictionaries are ignored.
- add a few more dependent complex types for testing
- fix UI issue which prevents dialogs from showing data
* workaround for dialogs with imagestream, always throwing exceptions
* rebuild with v1.04 modelcompiler
* Fixes#709 - Allow HTTPS clients to send the certificate for servers that require TLS client authentication
* Fixes#692 - HTTPS Server listener - Use the first configured policy for HTTPS
App registration for push servers from GDS client stopped working, maybe due to new db version in VS. But nulling the locale fixes the issue.
Note: DB should be recreated or the locale column must be manually set to nullable in the SQL Db.
#811 fixed
- add more tests verify how longer cert chains are built and verified with the cert validator
- some tweaks to cert factory to allow for building Sub CA certs
- allow to set the Basic Constraint / Path Length for CA certs
- fix#695 PKCS#8 format is now used
- add additional check to verify incomplete chain signatures
…instead of node id
It simplifies storage of cert group and type in attached db as string.
All GDS unit tests pass.
Breaking change (for GDS) due to interface change.
* add the Aes128 and Aes256 profiles
* Aes profies were tested on IoP workshop against Ascolab, Softing, Matrikon, Milo, ProSys and others
* Pss padding is not supported on all platforms, so autodetect if it is supported and filter out Aes256 if not
* not a breaking change: not specifying the SecurityProfileUri in the config xml will automatically add all supported profiles but not deprecated profiles (e.g. Basic256Sha256, Aes128, Aes256). Aes256 is only added if the platform supports Pss padding. This will simplify the maintenance of config xml, since automatically all supported and secure profiles are exposed.
- all changes for cloud based GDS
- build version of .net standard libs is now set in version.props, it may require updates for the official builds.
- add new stuff for v1.04 nodeset, e.g. QueryApplications Api
- gds.client/gds.server common dll changes to support a cloud based GDS.
* Fix for Mantis #4231. Refuse to use untrusted certificates to encrypt user identity tokens sent to servers.
* Deprecated security policies removed from default server config.xml files.
The AddRefrences method exists in similar versions in several of the sample node manager classes. The method loops through a list of (external) references and adds them to the designated objects. When obtaining node handles it also checks that the node is valid in the current context. The problem was that it skipped the rest of the nodes in the list as soon as it found one node that wass not valid. This change ensures that all nodes in the references list are processed.
- Fix the NO_HTTPS build to reduce publish size if HTTPS is not needed
e.g. `dotnet build /p:NoHttps=true`
- Limit language Version to C#6 for VS 2015 compat
- add travis & appveyor cases for nohttps build
- enable GDS Https transport
- update nuspec
- best possible fix for #189 to reenable https servers
- `UA Sample Client` and `UA Sample Server` expose https server. libuv.dll is by default for x64. Change
```
<PropertyGroup>
<RuntimeIdentifier>win7-x64</RuntimeIdentifier>
<BaseNuGetRuntimeIdentifier>win7-x64</BaseNuGetRuntimeIdentifier>
</PropertyGroup>
```
to win7-x86 if required.
- fix exception in https client when setting the Timeout
- fix travis build script for linux. kestrel server on ubuntu doesn't respond on ipv6Any ipaddress.
- fix a timing problem in the travis script.
- remove dependency on System.Private.ServiceModel, it should not be used directly
- remove packages.config, VS2017 doesn't need it
- use ref to .Net instead of nuget to reduce number of packages used
* Fixes for https client and server (#38)
HTTPS server fixes:
- Kestrel 2.0 in netcoreapp 2.0 server samples: only responds to some clients, not to UA samples at all. Fix configuration (listen to all ip addresses)
HTTPS client fixes:
- bug: client gets stuck if subscription is active by nesting too many calls (use async callback)
- https client needs server cert in a trusted store or it refuses connection (auto accept server certs, but fix is not supported on all platforms, e.g. UWP apps still require a cert in the trusted store)
- runtime issues with .Net 4.6. apps (cannot find diagnostics dll) --> workaround is to manually add nuget package of System.Net.http 4.3.3
- Add https connection to travis test script (only .Net Core)
* fix shell script exe
* also listen on ipv6 port
* do not use auto validation on OSX
Alin Moldovean