Note that the application is not "extensible". But if you mean in general out of interest: JavaFX and some 3rd party libs to it. For full list of components see Help->About->3rd party components, or (app.install.folder)/license/LICENSE.txt that lists individual components and their licenses.

Edit:
To my mind, the course is designed for very beginners and non-tech people, for them it would be a really good Introductory course but sure it wasn't for me...

bibhudatta.sahu@honeywell.com said
com.prosysopc.ua.stack.common.ServiceResultException: Bad_CertificateUseNotAllowed (code=0x80180000, description="Bad_CertificateUseNotAllowed (code=0x80180000, description="The certificate may not be used for the requested operation.")")

Hi, I came across this error message when I used a certificate which was missing the extensions 'Key Usage' and 'Extended Key Usage'. Certificates which were missing this extensions were working in older versions of several OpcUa servers, but when using such a certificate with newer versions of OpcUa Servers it might happen that the OpcUa Server rejects this certificate with the error message 'Bad_CertificateUseNotAllowed '

Please make sure that your certificate contains the follwoing extensions and have at least this values set...

This is code snippet of build/xml of JAR.

You must set the java system property “org.bouncycastle.rsa.allow_multi_use” to “true” in order for it to work. This can be done by example by starting the jvm with the flag “-Dorg.bouncycastle.rsa.allow_multi_use=true”. This is because OPC UA uses the same key for signing and encrypting, which by default is not allowed by the BC FIPS.

rajat said
Bouncy Casle FIPS needs different keys at Signing and Decryption:,
"Exception: Cannot Create Signer: cannot initialize for signing . Attempt to sign/verify with RSA modulus already used for encrypt/decrypt."
in order to achieve different keys at Signing and Decryption we need to Reregister Keys after Decryption by using new JcaX509v3CertificateBuilder , but its not allowing to reregister keys and giving giving Illegal Key Exception, java.lang.IllegalArgumentException: improperly specified input name: CN=Cisco SpeechView Client, E=ggnstt11@transcription.cisco.com, O=Cisco Systems, OU=UCBU, C=US

until service is restarted as if it maintains cache info in itself. Is this problem with Bouncy Castle FIPS  

is there any configuration to skip this error..??

Assuming this was related to our OPC UA SDK for java, https://forum.prosysopc.com/fo.....-java-sdk/ would be proper forum.

OPC UA use same key for both, no can do situation. If you can, pass flag "-Dorg.bouncycastle.rsa.allow_multi_use=true" and it should work.
See https://forum.prosysopc.com/fo.....tle/#p4700 for details.

bibhudatta.sahu@honeywell.com said
Hello,
I would like to know whether this Prosys SDK - 4.3 tested on QNX operating system environment. Is client able to connect to server running in QNX operating system.

Thanks,
Bibhudatta Sahu  

Hello,
Prosys OPC UA SDK for Java - 4.3 has NOT been tested on QNX. We think that it works on QNX, as it works on normal OSes, i.e. win/linux/osx, which would in general show that it works on a normal Java SE JVM. But to be sure, we are now setting up a test environment and confirm the compatibility.
By the way, as a commercial user, you can always send requests to our SDK support, which is quicker in response.

Thanks,
Bibhudatta Sahu

Also note that regardless of anything, I do not do in practice do live communications (would generally speaking be waste of time for everybody, since it could take hours to come up with proper answers, thus async communication channels are the way to go). Also it is vacation season here in Finland (usually from start of June to the end of August), thus it might take a while for a suitable person to be available. But in general sales will answer rest if you send mail to them.