This is an experimental technology
Because this technology's specification has not stabilized, check the compatibility table for usage in various browsers. Also note that the syntax and behavior of an experimental technology is subject to change in future versions of browsers as the specification changes.
The RTCIdentityEvent interface represents an identity assertion generated by an identity provider (idP). This is usually for an RTCPeerConnection. The only event sent with this type is identityresult..
Firefox implements this interface under the following name: RTCPeerConnectionIdentityEvent. It is likely that it will correct this name when it will unprefix RTCPeerConnection, once spec and implementation will have been stabilized.
Properties
A RTCIdentityEvent being an Event, this event also implements these properties.
RTCIdentityEvent.assertionRead only- Returns the
DOMStringcontaining a blob being the assertion generated.
Methods
A RTCIdentityEvent being an Event, this event also implements these properties. There is no specific RTCIdentityEvent method.
Examples
pc.onidentityresult = function( ev ) {
alert("A new identity assertion (blob: '" +
ev.assertion +
"') has been generated.");
}
Specifications
| Specification | Status | Comment |
|---|---|---|
| WebRTC 1.0: Real-time Communication Between Browser The definition of 'RTCIdentityEvent' in that specification. |
Working Draft | Initial definition. |
Browser compatibility
| Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari |
|---|---|---|---|---|---|
| Basic support | No support | (Yes) [1] | No support | (Yes) | ? |
| Feature | Android | Chrome for Android | Firefox Mobile (Gecko) | IE Mobile | Opera Mobile | Safari Mobile |
|---|---|---|---|---|---|---|
| Basic support | ? | ? | ? | No support | ? | ? |
[1] Gecko implements this interface under the following name: RTCPeerConnectionIdentityEvent.
See also
- WebRTC
- Its usual target:
RTCPeerConnection.