在此页

• 句法
• 描述
• 范例
• 规范
• 浏览器兼容性
• 相关话题

RTCConfiguration dictionary's optional certificates property is an array of RTCCertificate objects providing the security certificates available for use when authenticating duing the connection process.

句法

let rtcConfiguration = {
  certificates: certificateList
};
let rtcConfiguration.certificates = [ cert1... ];
let certificates = rtcConfiguration.certificates;
					

值

An array of RTCCertificate objects, each specifying one security certificate available for use when connecting to a remote peer. If this property isn't specified, the browser will automatically generate and use a certificate to secure the connection.

见 Using certificates below for more information on why you might want to—or not to—explicitly provide certificates.

描述

If this property isn't included in the configuration, a set of certificates is automatically generated for each instance of RTCPeerConnection . Although a given DTLS connection only uses a single certificate, providing multiple options in the certificates list may improve the odds of establishing a connection by increasing the chances a mutually-compatible encryption algorithm and key size may be found.

The method by which a browser decides which certificate to use is implementation-dependent. Some browsers may simply choose the first listed certificate and ignore the rest of the list; others may take a different approach.

Using certificates

When you wish to provide your own certificates for use by an RTCPeerConnection instead of having the RTCPeerConnection generate them automatically, you do so by calling the static RTCPeerConnection.generateCertificate() 函数。

certificates property's value cannot be changed once it's first specified. If it's included in the configuration passed into a call to a connection's setConfiguration() , it is ignored.

This attribute supports providing multiple certificates because even though a given DTLS connection uses only one certificate, providing multiple certificates allows support for multiple encryption algorithms. The implementation of RTCPeerConnection will choose which certificate to use based on the algorithms it and the remote peer support, as determined during DTLS handshake.

If you don't provide certificates, new ones are generated automatically. One obvious benefit to providing your own is identity key continuity—if you use the same certificate for subsequent calls, the remote peer can tell you're the same caller. This also avoids the cost of generating new keys.

<<<--- add link to information about identity --->>>

范例

此范例使用 RTCPeerConnection.generateCertificate() to create a certificate, then uses it to open a new RTCPeerConnection .

RTCPeerConnection.generateCertificate({
    name: 'RSASSA-PKCS1-v1_5',
    hash: 'SHA-256',
    modulusLength: 2048,
    publicExponent: new Uint8Array([1, 0, 1])
}).then(function(cert) {
  var pc = new RTCPeerConnection({certificates: [cert]});
});
					

规范

规范	状态	注释
WebRTC 1.0: Real-time Communication Between Browsers The definition of 'RTCConfiguration.certificates' in that specification.	候选推荐	初始定义。

浏览器兼容性

The compatibility table on this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request. 更新 GitHub 上的兼容性数据

	桌面						移动
	Chrome	Edge	Firefox	Internet Explorer	Opera	Safari	Android webview	Chrome for Android	Firefox for Android	Opera for Android	Safari on iOS	Samsung Internet
certificates	Chrome 23	Edge ≤79	Firefox ?	IE 不支持 No	Opera Yes	Safari ?	WebView Android Yes	Chrome Android 57	Firefox Android ?	Opera Android Yes	Safari iOS ?	Samsung Internet Android 7.0

图例

完整支持

完整支持

不支持

不支持

兼容性未知 ?

兼容性未知

元数据

• 最后修改： Aug 26, 2020

相关话题

1. RTCConfiguration
2. 特性

   1. bundlePolicy
   2. certificates
   3. iceServers
   4. iceTransportPolicy