Deprecated
This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
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.");
}
Browser compatibility
BCD tables only load in the browser
See also
- WebRTC
- Its usual target:
RTCPeerConnection
.