google-apigoogle-oauth

How to test Google's OAuth granular consent screen for TV & Device Apps


We received a notice from Google "OAuth clients must support granular consent, starting June 17, 2024". Our apps OAuth Client is TV and Limited-Input Devices.

We tested to display granular conscent OAuth scren using below scopes. "openid" "https://www.googleapis.com/auth/drive.file" "https://www.googleapis.com/auth/youtube.readonly"

However we cannot confirm the granular consent screen, in spite of after June 17.

OAuth test screen image

Does not an OAuth client for TV and Limited-Input Devices support granular consent? (We are hoping an OAuth client for TV and Limited-Input Devices don't support it.)

If it supports granular consent, we want to know how to display granular consent screen for TV and Limited-Input Devices.

OAuth Client is TV and Limited-Input Devices


Solution

  • I just confirmed that the granular permissions rollout would affect "TV and Limited Input devices" clients. The rollout has started and would slowly roll out to all clients. Hence, you may not see the granular permissions consent screen yet. I would suggest you do the following:

    1. If you need more time to update, test, deploy your code to support granular permissions, please follow the steps in the email ("OAuth clients must support granular consent, starting June 17, 2024") you received to request an extension.

    2. Follow "Best practices to handle granular permissions" to update your applications to handle partial consent. The SDKs you mentioned should support that. Essentially, you want to check what kind of scopes users authorized. Before granular permissions rollout, you can assume if users authorized your requests, all the scopes are granted. After the rollout, you can't assume all scopes are granted. Hence, you need to check which scopes are granted and update your application functionalities accordingly.

    3. See "Test your updated application on handling granular permissions" on how to test your application by enabling granular permissions before the rollout.