中风险
升级后默认请求经验证的电子邮箱
原文依据：5 处发现了什么
迁移说明称 InternetIdentityProvider 默认启用属性验证并请求 verified_email。未显式关闭时，用户登录会被提示共享邮箱；这是从原本普通登录增加的个人数据披露。
为什么需要注意
用户的经验证邮箱可能被提供给身份验证流程及使用该属性的应用后端，从而把可关联身份的信息加入账户或业务数据。
迁移说明明确表示，升级后的 InternetIdentityProvider 默认启用属性验证并请求 verified_email；应用未显式关闭时，登录用户会看到共享邮箱的提示。这支持个人数据披露风险，但证据仅是文档中的默认行为说明，不能证明邮箱已被收集或发送。用户可要求应用说明邮箱用途、接收方和保存方式，或确认其设置 withAttributes={false} 以退出该请求。
`InternetIdentityProvider` now enables attribute verification by default. Existing apps that do not need email attributes must opt out explicitly.查看另外 4 个位置
### 3. `InternetIdentityProvider` attribute verification is now on by default`withAttributes` now defaults to `{}` (enabled, requesting `verified_email`). This is a non-breaking addition from Internet Identity — existing apps continue to work as before, and users are simply prompted to share their email during sign-in. No code change is required unless you want to opt out entirely:```tsx// opt out — plain sign-in, no attribute request<InternetIdentityProvider withAttributes={false}>```- Sessions from all variants are stored the same way: `isAuthenticated`, session restore on reload, and `clear()` behave identically regardless of the variant used.- When the backend uses `caffeineai-authorization`, Google, Microsoft, and SSO sign-ins carry verified name/email attributes (and the SSO domain) to the attribute callback automatically — see the `extension-authorization` skill.`withAttributes` now defaults to `{}` (enabled, requesting `verified_email`). This is a non-breaking addition from Internet Identity — existing apps continue to work as before, and users are simply prompted to share their email during sign-in. No code change is required unless you want to opt out entirely:```tsx// opt out — plain sign-in, no attribute request<InternetIdentityProvider withAttributes={false}>```