This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The RTCIdentityErrorEvent
interface represents an error associated with the identity provider (idP). This is usually for an RTCPeerConnection
. Two events are sent with this type: idpassertionerror
and idpvalidationerror
.
Firefox implements this interface under the following name: RTCPeerConnectionIdentityErrorEvent.
It is likely that it will correct this name when it will unprefix RTCPeerConnection
, once spec and implementation will have been stabilized.
Properties
A RTCIdentityErrorEvent
being an Event
, this event also implements these properties.
RTCIdentityErrorEvent.idp
Read only- Is a
DOMString
describing the domain name of the identity provider (idp) generating the error response. RTCIdentityErrorEvent.loginUrl
Read only- Is a
DOMString
giving the URL where the user can complete the authentication. It can benull
and is provided by the identity provider (idp). RTCIdentityErrorEvent.protocol
Read only- Is a
DOMString
describing the Idp protocol in use.
Methods
A RTCIdentityErrorEvent
being an Event
, this event also implements these properties. There is no specific RTCIdentityErrorEvent
method.
Examples
pc.onidpassertionerror = function( ev ) { alert("The idp named '" + ev.idp + "' encountered an error " + "while generating an assertion."); }
Specifications
Specification | Status | Comment |
---|---|---|
WebRTC 1.0: Real-time Communication Between Browsers The definition of 'RTCIdentityErrorEvent' in that specification. |
Candidate Recommendation | Initial definition. |
Browser compatibility
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
RTCIdentityErrorEvent | Chrome No support No | Edge ? | Firefox
Full support
Yes
| IE No support No | Opera Full support Yes | Safari ? | WebView Android No support No | Chrome Android No support No | Firefox Android ? | Opera Android ? | Safari iOS No support No | Samsung Internet Android No support No |
idp | Chrome No support No | Edge ? | Firefox ? | IE No support No | Opera Full support Yes | Safari ? | WebView Android No support No | Chrome Android No support No | Firefox Android ? | Opera Android ? | Safari iOS No support No | Samsung Internet Android No support No |
loginUrl | Chrome No support No | Edge ? | Firefox ? | IE No support No | Opera Full support Yes | Safari ? | WebView Android No support No | Chrome Android No support No | Firefox Android ? | Opera Android ? | Safari iOS No support No | Samsung Internet Android No support No |
protocol | Chrome No support No | Edge ? | Firefox ? | IE No support No | Opera Full support Yes | Safari ? | WebView Android No support No | Chrome Android No support No | Firefox Android ? | Opera Android ? | Safari iOS No support No | Samsung Internet Android No support No |
Legend
- Full support
- Full support
- No support
- No support
- Compatibility unknown
- Compatibility unknown
- Experimental. Expect behavior to change in the future.
- Experimental. Expect behavior to change in the future.
- Uses a non-standard name.
- Uses a non-standard name.
See also
- WebRTC
- Its usual target:
RTCPeerConnection
.