我应该为第 3 方 API 拥有一个电子邮件/用户帐户，还是为每个 API 拥有一个单独的电子邮件/用户帐户？
在业务场景中，是否有针对第三部分 API 使用电子邮件/用户帐户的最佳实践？ 例如，假设我的公司域名是 foo.com，我需要访问来自 Flicker、youtube、twitter、facebook、jigsaw、Amazon、ebay 等的数据。 我是否应该有单独的电子邮件地址/用户名，例如[电子邮件受保护]，< a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="87fee8f2f3f2e5e2e6eef7c7e1e8e8a9e4e8ea">[电子邮件受保护], [email protected] 或类似 [电子邮件受保护] 并在需要单独用户名的服务中使用一致的用户名？你做什么工作？两者之间有什么缺点或优点吗？对我来说，多个电子邮件地址的明显缺点是记住所有电子邮件地址。
Is there a best practice for using email/user accounts for 3rd part APIs in a business scenario?
For example say my company domain is foo.com, and I need to access data from Flicker, youtube, twitter, facebook, jigsaw, Amazon, ebay, and many others.
Should I have seperate email addresses/user names like [email protected],[email protected], [email protected] or something like [email protected] and have a consitent username used across services if they require a seperate user name? What do you do? Are there any disadvantages or advantages to one or the other? The obvious disadvantage to me of multiple would be remembering all the email addresses.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这个问题的答案有很多方面，我认为显然没有任何单一的更好的方法。
为了安全起见，您应该计划拥有多个，以防万一您尝试预订的那个已被占用（这种情况很少见，但确实会发生）。这样您就可以计划使用单个产品，但如果您的设计中的某些内容必须更改，您也可以做好准备。
剩下的就是关于可见性，以及你想要如何规避风险。每项服务拥有一个帐户意味着，如果一个帐户遭到泄露（密码被发现等），那么它是唯一受影响的帐户（假设您为每项服务使用不同的凭据）。缺点是很明显这些都指向同一个地方（不一定是坏事），滥用其中一个可能会导致其他地方出现问题。
拥有多个帐户可以缓解其中的一些问题，但您还有其他令人头疼的问题，例如多个密码、管理多个过期流程以及审核以确保所有帐户仍然有效等。
There are many facets to the answer for this question, and I dont think there is obviously any single superior way.
To be safe you should plan on having multiple, just in case the one you are trying to reserve is already taken (its rare, but it happens). That way you can plan on using a single one but you are prepared if something in your design has to change.
The rest is about visibility, and how risk-averse you want to be. Having one account per service means that if one is compromised (password is discovered, etc) its the only one affected (assuming you use different credentials for each). The downside is that its very obvious these all point to the same place (not necessarily bad) and abuse of one could lead to problems in other places.
Having multiple accounts mitigates some of this, but you have other headaches, such as multiple passwords, managing multiple expiration processes, and auditing to make sure the accounts all still work, etc.