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.
pc.getIdentityAssertion();
There is neither parameter nor return value for this method.
var pc = new PeerConnection(); pc.getIdentityAssertion(); // Not mandatory, but we know that we will need it in the future.
Specification | Status | Comment |
---|---|---|
WebRTC 1.0: Real-time Communication Between Browsers The definition of 'RTCPeerConnection.getIdentityAssertion()' in that specification. | Candidate Recommendation | Initial specification. |
Desktop | ||||||
---|---|---|---|---|---|---|
Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | |
Basic support | 56 | Yes | 22 | ? | 43
|
? |
Mobile | |||||||
---|---|---|---|---|---|---|---|
Android webview | Chrome for Android | Edge Mobile | Firefox for Android | Opera for Android | iOS Safari | Samsung Internet | |
Basic support | 56 | 56 | Yes | 44 | 43
|
? | 6.0 |
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/getIdentityAssertion