Hi everyone

so I am using client SDK in Version 4.10.6-24 and observe a very strange behavior when connecting to a S7-1500 OPC UA Server.
So first of all, my code using/calling the prosys library is packaged into a jar-library (“lib A”) and this library is embedded in a specific application (“app A”), which works fine using whatever combination of connection parameterization.
In another application (“app B”), using the exact same library “lib A”, it fails.
But it fails only when using the combination User+SignAndEncrypt+Basic256Sha256, anonymous and “just user” works fine.
The initial assumption was that there were problems with certificates, but we were able to rule that out because we used the same certificate and the same truststore. Also the S7 was configured to trust any certificate.
The most bizarre part is that the S7 logs show that the session is created, but after 30 seconds it times out and gets removed from the server. (30 seconds session timeout is configured on server side).
From the client-side logs I could observe that the whole 30 seconds, the code is seemingly stuck within UaClient#connect().

I can only assume that it is related to some crypto library. My “lib A” jar comes with bouncycastle 1.71 and spongycastle 1.58.0.0.
So my question is:
1. why and how can the connect() get stuck after the session has been created?
2. can i figure out which crypto-library the sdk uses?

Thanks for any hints!