Client still gives BadCertificateInvalid when Security Policy is None and Server isn't sending any certificates

[debajyotisarkarhome]

[debajyotisarkarhome]

This is what I'm using to connect

let mut client = ClientBuilder::new()
                .application_name("PLC OPC UA Client")
                .application_uri(&format!("urn:{}", config.conn_ip))
                .trust_server_certs(true)
                .verify_server_certs(false)
                .session_retry_limit(0)
                .client()
                .map_err(|e| format!("Failed to create OPC UA client: {:?}", e))?;

            let endpoint: EndpointDescription = (
                format!("opc.tcp://{}:4840", config.conn_ip).as_str(),
                SecurityPolicy::None.to_str(),
                MessageSecurityMode::None,
                UserTokenPolicy::anonymous(),
            ).into();

            let (session, event_loop) = client
                .connect_to_matching_endpoint(endpoint, IdentityToken::Anonymous)
                .await
                .map_err(|e| format!("Failed to connect to OPC UA server {}: {:?}", config.conn_ip, e))?;

            let mut handle = event_loop.spawn();
            session.wait_for_connection().await;

[einarmo]

Are you sure the certificate is empty and not just some garbage? Or perhaps something stupid like a literal "null"? I don't see how this would happen, and I can't reproduce on my end.

[einarmo]

It must be here:

async-opcua/async-opcua-crypto/src/x509.rs

Line 619 in 0b3452d

Err(e) => Err(Error::new(StatusCode::BadCertificateInvalid, e)),

, but that error would look different if is_null_or_empty returned true, so clearly it's something else, that's neither an empty string or a null value.