- 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
* Update for 1.04 attributes in ClientSession.ReadNode()
* Fix in ClientSession.ReadNode()
* Updates for 1.04 Attributes in server.
* Discard inner value for attributes with bad status codes in ClientSession.ReadNode().
* Remove unused attribute from AttributeWriteMask
Fixed wrong null checks for Notification message in GetServiceResult(IEncodeable notification) and GetServiceResult(IEncodeable notification, int index)
…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.
The AddRefrences 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 belongs to one of the namspaces for the current node manager. The problem was that it skipped the rest of the nodes in the list as soon as it found one node that did not belong to the currennt node manager.
ejoseca