This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The RTCPeerConnection.getIdentityAssertion() method initiates the gathering of an identity assertion. This has an effect only if the signalingState is not "closed".
The method returns immediately. If the assertion cannot be generated, an idpassertionerror will be sent to the object.
It is not expected for the application dealing with the RTCPeerConnection: this is automatically done; an explicit call only allows to anticipate the need.
Syntax
pc.getIdentityAssertion();
There is neither parameter nor return value for this method.
Example
var pc = new PeerConnection(); pc.getIdentityAssertion(); // Not mandatory, but we know that we will need it in the future.
Specifications
| Specification | Status | Comment |
|---|---|---|
| WebRTC 1.0: Real-time Communication Between Browsers The definition of 'RTCPeerConnection.getIdentityAssertion()' in that specification. |
Candidate Recommendation | Initial specification. |
Browser compatibility
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.
| Feature | Chrome | Edge | Firefox | Internet Explorer | Opera | Safari |
|---|---|---|---|---|---|---|
| Basic support | 56 | Yes | 22 | ? | 431 37 — 43 | ? |
| Feature | Android webview | Chrome for Android | Edge mobile | Firefox for Android | Opera Android | iOS Safari | Samsung Internet |
|---|---|---|---|---|---|---|---|
| Basic support | 56 | 56 | Yes | 44 | 431 37 — 43 | ? | 6.0 |
1. Promise based version.