TURN OAuth tokens

[BP Gangadharan]

http://tools.ietf.org/html/draft-ietf-tram-turn-third-party-authz-12

Is there a way to pass the OAuth tokens defined in the above document to chrome browser?

[Justin Uberti]

not yet, we first need to add it to the w3c spec as RTCIceServer.authToken

On Wed, Feb 25, 2015 at 3:28 AM, BP Gangadharan <bp.gang...@gmail.com> wrote:

http://tools.ietf.org/html/draft-ietf-tram-turn-third-party-authz-12

Is there a way to pass the OAuth tokens defined in the above document to chrome browser?

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[BP Gangadharan]

Thanks for the reply. 

Would this get into the spec (and chrome) any time soon?

[Justin Uberti]

PR outstanding: https://github.com/w3c/webrtc-pc/pull/192

[BP Gangadharan]

Great. Thanks.

[BP Gangadharan]

Is this (eg: ACCESS-TOKEN stun attribute) supported in chrome now? 

[Justin Uberti]

It is in the working copy of the spec now, but not yet supported in Chrome.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/b4c22715-d543-4b0e-b886-bd2ea374035b%40googlegroups.com.

[Mihály Mészáros]

I am wondering how should I add OAuth token and session key to the peerconection iceServer config?

AFAIU OAuth has (according RFC 7635) the key id(kid) as username,
and has two "credential" information pieces, that are needed to pass to the browser ICE agent:

1. the Session Key(Message Integrity, HMAC key).
2. the Access Token (SelfContaing token, e.g. Authenticated-Encryption with Associated-Data(AEAD) encrypted token.)
   

But in WebIDL I could find only one DOMString for Credential.

dictionary RTCIceServer {
    required (DOMString or sequence<DOMString>) urls;
             DOMString                          username;
             DOMString                          credential;
             RTCIceCredentialType               credentialType = "password";
};

And furthermore this credential field is normally in case of "password" auth (Long Term Credential)  contains the Session Key(Message Integrity, HMAC key).

I am wondering what is the right way?

1. Is it possible to add a new field for the OAuth token? (I would prefer this way.)
   
2. Or the intended method is to put both (the Session Key and the OAuth token) somehow packed in one string.
   e.g. put all in one JSON object, and add this way into the credential field? (If so, is there any suggested format of the JSON?)
   

Any comment highly appreciated!

[Hitesh Chouhan]

Hi Justin,

Is the support for OAuth tokens available in Chrome (M60) now? Thanks.

[Basar Daldal]

Hi,

Is there any update on the support of oAuth credentials for TURN access?

Thanks.

[Basar Daldal]

Hi,

I want to ask the same question again, is OAuth for TURN access supported in Chrome?

Thanks,

Basar

[Taylor Brandstetter]

It isn't. Here's a bug for Chrome and one for Firefox.

To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/2d6354ed-3f9b-4c17-854e-6eb028563b3f%40googlegroups.com.