Google OAuth 同意屏幕仍然显示令人困惑的范围复选框

发布于 2025-01-09 17:56:29 字数 1342 浏览 4 评论 0 原文

我在此处这里,但解决方案对我们不起作用。我们的用户对这些复选框感到困惑,因为他们以前没有在其他应用程序上看到过它们,这让他们对它们提供的访问权限更加偏执。

我们的应用程序需要联系人和日历只读访问功能,我尝试了其他人提到的许多技巧,但没有一个起作用:

  • 我们在Cloud Console范围中添加了电子邮件、个人资料、openid,复选框仍然出现
  • 我们将登录与授权分开访问时,复选框仍然出现。

我们错过了什么吗? 看起来如果我们只请求1个权限或许可以解决问题,但是要求用户打开3个弹窗授权访问就太不方便了。

输入图片此处描述

向 Google 团队提供反馈:。 细化权限绝对是保护用户隐私的正确方向, 但是:

  • 流程会惩罚具有细化权限的应用程序(例如,如果我要求所有 calendars.readonly 和 events.readonly,这些强制显示 2 复选框,而如果我只请求 1 个超级权限,例如 Calendly 的“编辑/管理/删除所有日历和事件”,它没有 显示一个复选框。
  • 给用户带来很多不便和不必要的恐惧。
  • 并非所有应用都具有相同的细化权限,它会奖励尚未受到细化权限影响的旧应用(例如 Calendly) 权限,而新应用程序本质上处于不利地位。

想法:

  • 允许应用开发者选择哪些权限是可选的,哪些是必需的
  • 添加一个说明字段,在向最终用户请求的每个权限旁边显示实用程序,并且可以将其添加到应用程序审核中 敏感范围的流程。
  • 只需点击 1-2 次鼠标即可超级流畅地授权新权限,而不是打开弹出窗口。想想移动应用程序如何请求联系人 权限,它是精细的、上下文相关的,只需点击 1 次即可。

I've seen other questions who shared this same issue here and here, but the solutions are not working for us. Our users are confused with the checkboxes since they haven't seen them on other apps before and it's making them more paranoid about the access they give.

Our app requires contacts and calendar read-only access to function, and i've tried many tricks mentioned by others but none of them worked:

  • We added email, profile, openid in Cloud Console scopes, the checkboxes still appear
  • We split login from authorization access, the checkboxes still appear.

Are we missing anything?
It seems if we only ask for 1 permission, it might solve the problem, but it's too inconvenient to ask the user to open 3 popups to authorize access.

enter image description here

Feedback to Google Team:.
Granular permissions are definitely in the right direction for user privacy,
but:

  • Process penalizes apps with granular permissions (e.g. if i ask for all calendars.readonly, and events.readonly, those force to show 2
    checkboxes, whereas if i ask for only 1 super permission like
    Calendly's "edit/manage/delete all calendars and events", it doesn't
    show a checkbox.
  • Introduces a lot of inconvenience and unnecessary fear for the user.
  • Not all apps have the same granular permissions, and it's rewarding old apps (like Calendly) who are not yet impacted by granular
    permissions, whereas new apps are inherently disadvantaged.

Ideas:

  • Allow app developers to select which permissions are optional vs required
  • Add an explanation field that shows the utility next to each permission requested to the end-user, and this could be added to the app review
    process for sensitive scopes.
  • Make authorizing new permissions super fluid 1-2 clicks away, instead of opening a popup. Think how mobile apps ask for contacts
    permission, it's granular, contextual and only 1 click away.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

黯淡〆 2025-01-16 17:56:29

您提到的解决方法可能有效,但 Google 自 2018 年以来似乎已宣布对此行为进行此更改。看起来,当应用程序请求来自不同服务的访问时,就会发生此行为 Strobe 项目博客

如果您的应用程序向不同服务请求权限,则无法直接删除细化范围,因为这将强制显示细化权限。

The workarounds that you mentioned may work but it seems that Google has announced this change on this behavior since 2018. Looks like the behavior happens when the app is requesting access from different services as noted in this Project Strobe blog.

There will be no direct way to remove the granular scopes if your app would be requesting permissions from different services as this will force the granular permissions to show up.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文