Discussion:
[OAUTH-WG] Cross Platform Authentication - OAuth 2.0 Device Flow
Barroco, Michael
2016-03-07 08:43:56 UTC
Permalink
Dear all,


We are contacting you because we noticed that you recently restarted the work on OAuth 2.0 Device Flow. We are in the process of publishing an ETSI standard [1] specifying a protocol with very similar goals. This has been developed by an EBU (European Broadcasting Union) working group involving broadcasters, such as BBC, SRG-RTS, VRT, RTVE, TVP, Global Radio UK, and device manufacturers.


Our work on the “Cross Platform Authentication” protocol targets media devices, such as connected TVs and radio receivers. It is based on the early OAuth 2.0 Device Flow draft, but includes additional features driven by broadcast industry requirements. These include: dynamic registration of clients, dynamic discovery of the authorization provider, and issuing of access tokens without requiring association with a user account in order to provide device-based authentication that does not require user sign-in or pairing. Our draft protocol specification is available here [2].


Cross Platform Authentication also specifies several aspects left open to implementers in OAuth 2.0, such as endpoint URL paths, to facilitate interoperability. Also note that reference implementations are available [3].


We would be very interested in working together with you to explain our design requirements and try to align our protocol designs.


With best regards,


The EBU Cross Platform Authentication group

https://tech.ebu.ch/cpa



[1] https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=47970


[2] https://tech.ebu.ch/docs/tech/tech3366.pdf

[3] https://tech.ebu.ch/code/cpa
Hannes Tschofenig
2016-03-11 09:47:05 UTC
Permalink
Hi Michael,

thanks for dropping us a note since I was not aware of the EBU work.
It is always intesting to hear from other communities who have been able
to make use of OAuth for their use cases.

I will take a look at your specification to better understand what you
have been doing in your working group.

Ciao
Hannes
Post by Barroco, Michael
Dear all,
We are contacting you because we noticed that you recently restarted
the work on OAuth 2.0 Device Flow. We are in the process of
publishing an ETSI standard [1] specifying a protocol with very
similar goals. This has been developed by an EBU (European
Broadcasting Union) working group involving broadcasters, such as
BBC, SRG-RTS, VRT, RTVE, TVP, Global Radio UK, and device
manufacturers.
Our work on the “Cross Platform Authentication” protocol targets
media devices, such as connected TVs and radio receivers. It is based
on the early OAuth 2.0 Device Flow draft, but includes additional
dynamic registration of clients, dynamic discovery of the
authorization provider, and issuing of access tokens without
requiring association with a user account in order to provide
device-based authentication that does not require user sign-in or
pairing. Our draft protocol specification is available here [2].
Cross Platform Authentication also specifies several aspects left
open to implementers in OAuth 2.0, such as endpoint URL paths, to
facilitate interoperability. Also note that reference implementations
are available [3].
We would be very interested in working together with you to explain
our design requirements and try to align our protocol designs.
With best regards,
The EBU Cross Platform Authentication group
https://tech.ebu.ch/cpa
[1]
https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=47970
[2] https://tech.ebu.ch/docs/tech/tech3366.pdf
[3] https://tech.ebu.ch/code/cpa
------------------------------------------------------------------------------
************************************************** This email and
any files transmitted with it are confidential and intended solely
for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system
manager. This footnote also confirms that this email message has been
swept by the mailgateway
**************************************************
_______________________________________________ OAuth mailing list
Loading...