RTCDtlsTransport-fingerprint-error.https.html

Enable keyboard shortcuts

This WPT test may be referenced by the following Test IDs:
- /webrtc/RTCDtlsTransport-fingerprint-error.https.html - WPT Dashboard Interop Dashboard

<!doctype html>

<meta charset=utf-8>

<title>Bug 1805447: Check that fingerprint error is surfaced on other side as "dtls-failure"</title>

<script src="/resources/testharness.js"></script>

<script src="/resources/testharnessreport.js"></script>

<script src="/webrtc/RTCPeerConnection-helper.js"></script>

<script>

"use strict";

// https://w3c.github.io/webrtc-pc/#dom-rtcerrordetailtype-fingerprint-failure

// Says 'If the remote peer cannot match the local certificate against the

// provided fingerprints, this error is not generated. Instead a

// "bad_certificate" (42) DTLS alert might be received from the remote peer,

// resulting in a "dtls-failure".'

// Note the word "might"; there is no spec guarantee that this is surfaced, so

// this isn't web-platform-testable. :(

promise_test(async t => {

  const offerer = new RTCPeerConnection();

  const answerer = new RTCPeerConnection();

  t.add_cleanup(() => offerer.close());

  t.add_cleanup(() => answerer.close());

  const stream = await getNoiseStream({ audio: true });

  offerer.addTrack(stream.getTracks()[0]);

  exchangeIceCandidates(offerer, answerer);

  await offerer.setLocalDescription();

  let badSdp = offerer.localDescription.sdp;

  // Tweak the last digit in the fingerprint sent to the answerer. Answerer

  // (which will be the DTLS client) will see the bad cert, send a

  // "bad_certificate" alert, and fire a "fingerprint-failure" error.

  const lastDigit = badSdp.match(/a=fingerprint:.*([0-9A-F])$/m)[1];

  const newLastDigit = lastDigit == '0' ? '1' : '0';

  badSdp = badSdp.replace(/(a=fingerprint:.*)[0-9A-F]$/m, "$1" + newLastDigit);

  await answerer.setRemoteDescription({sdp: badSdp, type: "offer"});

  await answerer.setLocalDescription();

  const answererTransport = answerer.getSenders()[0].transport;

  const answererErrorPromise = new Promise(r => {

    answererTransport.onerror = r;

});

  await offerer.setRemoteDescription(answerer.localDescription);

  const offererTransport = offerer.getSenders()[0].transport;

  const offererErrorPromise = new Promise(r => {

    offererTransport.onerror = r;

});

  const answererError = await answererErrorPromise;

  assert_true(answererError instanceof RTCErrorEvent);

  assert_true(answererError.error instanceof RTCError);

  assert_equals(answererError.error.errorDetail, "fingerprint-failure");

  assert_equals(answererError.error.sentAlert, null);

  assert_equals(answererError.error.receivedAlert, null);

  assert_not_equals(answererError.error.message.length, 0);

  assert_equals(answererError.error.name, 'OperationError');

  const offererError = await offererErrorPromise;

  assert_true(offererError instanceof RTCErrorEvent);

  assert_true(offererError.error instanceof RTCError);

  assert_equals(offererError.error.errorDetail, "dtls-failure");

  assert_equals(offererError.error.sentAlert, null);

  // bad_certificate is 42, see

  // https://datatracker.ietf.org/doc/html/rfc8446#appendix-B.2

  // This is pretty much the only DTLS alert content can cause.

  assert_equals(offererError.error.receivedAlert, 42);

  assert_not_equals(offererError.error.message.length, 0);

  assert_equals(offererError.error.name, 'OperationError');

}, 'fingerprint error is surfaced on other side as "dtls-failure"');

</script>