Bad ReceiverCertificateThumbprint in OpenSecureChannel message?

[GrantEdwards]

I can't get encryption working with the opcua-asyncio client-with-encyrption example.

The server is rejecting the OpenSecureChannel message sent by the example client because the ReceiverCertificateThumbprint field contains garbage. When I open a similar connection with the UAExpert client, it works fine: the UAExport client sends the thumbprint of the OPC UA server's certificate as expected. I can't figure out where the data in that field comes from when using the opcua-asyncio client: it's not the thumbprint of any of the certificates involved.

Does the client with encryption work for anybody else with a server that validates the ReceiverCertificateThumbprint field?

[GrantEdwards]

Ah, I missed the fact that in that example the server certificate is being set explicitly with the set_security() call (and it's not the real server's certificate). Removing the server_certificate parameter from that call fixes the failure.