Open
Bug 1538778
Opened 6 years ago
Updated 2 years ago
When the idp fails to validate an identity assertion, RTCPeerConnection.peerIdentity should be rejected with an OperationError
Categories
(Core :: WebRTC: Signaling, enhancement, P2)
Core
WebRTC: Signaling
Tracking
()
NEW
People
(Reporter: bwc, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [wpt-triaged])
Right now we reject with the same error the idp gave us:
Error thrown here: https://searchfox.org/mozilla-central/rev/2c912888e3b7ae4baf161d98d7a01434f31830aa/dom/media/PeerConnection.jsm#984
peerIdentity rejected with the error here: https://searchfox.org/mozilla-central/rev/2c912888e3b7ae4baf161d98d7a01434f31830aa/dom/media/PeerConnection.jsm#1002
Reporter | ||
Comment 1•6 years ago
|
||
The spec seems to say that sRD should be rejected with the same OperationError too, although it is a little ambiguous.
Updated•5 years ago
|
Whiteboard: [wpt-triaged]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•