The sample server (server_ctt) built using open62541 v1.0 is in conformance with the 'Micro Embedded Device Server' Profile of OPC Foundation supporting OPC UA client/server communication, subscriptions, method calls and security (encryption) with the security policies 'Basic128Rsa15', 'Basic256' and 'Basic256Sha256' and the facets 'method server' and 'node management'.
PubSub (UADP) is implemented in open62541. But the feature cannot be certified at this point in time (Sep-2019) due to the lack of official test cases and testing tools.
open62541 is maintained by a community of developers and users. The certified release v1.0 was prepared by Fraunhofer IOSB and Kalycito Infotech with funding from an industry consortium via the Open Source Automation Development Lab (OSADL) eG.
Fraunhofer IOSB is responsible for the overall architecture of open62541 and maintains the project jointly with a cross-organizational team from research and industry.https://www.iosb.fraunhofer.de/
Kalycito Infotech provides consulting, software integration services and commercial support for customers interested in integrating open62541 into their products and getting them certified.https://www.kalycito.com/opc-ua-sdk/
The Open Source Automation Development Lab (OSADL)eG based in Heidelberg, Germany provides support for industry when using Open Source software in products.https://www.osadl.org/
OPC Foundation Certified for Compliance logo is a trademark of the OPC Foundation and may be used only by written permission of the OPC Foundation. Any unauthorized use of the Certified for Compliance logo is prohibited. OPC Foundation Certified for Compliance logo indicates that this product has been tested by an independent certification lab and certified to be compliant with the following OPC UA Profiles which are part of the OPC UA Specifications:
Additional information about compliance testing, logo program and a summary of test results can be found at www.opcfoundation.org for: Open62541 OPC UA Server (server_ctt) 1.0.0-rc5.
The precise version used for the certification has the commit hash 1135945fe8eb8e4e9df7694e5d564443a6d4df80 . Later releases in the 1.0 release family contain only bugfixes in comparison to the certified version.