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 |
---|---|---|
Identity for WebRTC 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.
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
getIdentityAssertion | Chrome No support No | Edge No support ≤18 — 79 | Firefox Full support 22 | IE No support No | Opera
Full support
43
| Safari ? | WebView Android No support No | Chrome Android No support No | Firefox Android Full support 44 | Opera Android
Full support
43
| Safari iOS ? | Samsung Internet Android Full support 6.0 |
Legend
- Full support
- Full support
- No support
- No support
- Compatibility unknown
- Compatibility unknown
- See implementation notes.
- See implementation notes.