IdP

[robin-raymond]

Need to add related interface(s)/dictionaries

[aboba]

Progress on this issue is awaiting the next WebRTC 1.0 editor's draft, which we presume will include some IdP updates from Martin Thomson.

[aboba]

Does the following make sense for integration of the idP material in Section 8 of the WebRT 1.0 document?

partial interface RTCDtlsTransport {
void setIdentityProvider (DOMString provider, optional DOMString protocol, optional DOMString username);
void getIdentityAssertion ();
readonly attribute RTCIdentityAssertion? peerIdentity;
attribute EventHandler onidentityresult;
attribute EventHandler onpeeridentity;
attribute EventHandler onidpassertionerror;
attribute EventHandler onidpvalidationerror;
};

[martinthomson]

You'll want to have a setIdentityAssertion(DOMString assertion) as well, since you aren't feeding this with setRemoteDescription any more.

With that, you could probably remove some of the indirection.

How about reducing the surface area a little:

partial interface RTCDtlsTransport {
    Promise<DOMString> getIdentityAssertion(DOMString provider, optional DOMString protocol = "default", optional DOMString username);
    // this encapsulates onidentityresult and onidpassertionerror in the promise
    Promise setIdentityAssertion(DOMString assertion);
    // this encapsulates onidentityresult and onidpvalidationerror

    readonly attribute RTCIdentityAssertion? peerIdentity;
};

[robin-raymond]

@martinthomson I like this API overall. I would make it its own interface though that is constructed from a RTCDtlsTransport to keep the security assertion stuff separate from DTLS, or we could make it like stats interface where "secure" transports could derive from...

[aboba]

A potential proposal:
http://lists.w3.org/Archives/Public/public-ortc/2014Jul/0017.html