- From: Louay Bassbouss via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 May 2018 13:51:25 +0000
- To: public-secondscreen@w3.org
@Mathieu-R it is not a good practice to handle Authentication on receiver device. As solution to present protected content could be: - Do authentication on sender device - Generate token (may expires after some time) and send it to receiver device. - receiver application requests content from server using that token. If you don't have have full control on receiver application it will be difficult to solve the issue -- GitHub Notification of comment by louaybassbouss Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/448#issuecomment-387071162 using your GitHub account
Received on Monday, 7 May 2018 13:51:33 UTC