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. |
Working Draft | Initial specification. |
Browser compatibility
Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari |
---|---|---|---|---|---|
Basic support | No support | (Yes) [1] | No support | (Yes) | ? |
Feature | Android Webview | Chrome for Android | Firefox Mobile (Gecko) | IE Mobile | Opera Mobile | Safari Mobile |
---|---|---|---|---|---|---|
Basic support | No support | No support | ? | No support | ? | ? |
[1] Though this property is not prefixed, the interface it belongs to is.