W3C home > Mailing lists > Public > public-ortc@w3.org > July 2014

Re: Issue 78: IdP

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Fri, 4 Jul 2014 00:22:20 +0000
To: "public-ortc@w3.org" <public-ortc@w3.org>
Message-ID: <2a7be90990184462a4864d728ac7b514@SN2PR03MB031.namprd03.prod.outlook.com>
Martin Thomson said: 

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] said: 

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...

[BA]  How about this? 

[Constructor(RTCDtlsTransport transport)]
interface RTCIdentity {
    readonly    attribute RTCIdentityAssertion? peerIdentity;
    readonly    attribute RTCDtlsTransport      transport;
    Promise<DOMString>            getIdentityAssertion (DOMString provider, optional DOMString protocol = "default", optional DOMString username);
    Promise<RTCIdentityAssertion> setIdentityAssertion (DOMString assertion);
};

dictionary RTCIdentityError {
    DOMString  idp;
    DOMString  protocol;
    DOMString? loginUrl;
};

dictionary RTCIdentityAssertion {
    DOMString idp;
    DOMString name;
};
Received on Friday, 4 July 2014 00:22:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:05:18 UTC