Azure ACS 初学者方法
我知道有很多关于 Azure ACS 的问题，但我想问一个更普遍的问题：
我应该使用 ACS，还是不值得付出努力？ :)
我想要的是 Azure 中的安全 WebService，它将从 2 个位置调用：移动应用程序和 Azure 内的另一个服务。用户永远不会直接访问此 webService。
谢谢
更新： 我不太关心我的移动应用程序背后的用户身份。
I know there are a lot of questions about Azure ACS, but I want to ask a more general one:
Should I use ACS, or it's not worth the effort? :)
What I want is a secure WebService in Azure that will be called from 2 places: a mobile app and another service inside Azure. Users will never access this webService directly.
Thanks
Update:
I don't care much about the identity of the user that is behind my mobile app.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我认为这取决于具体的场景，你说用户不会直接访问该服务，但大概是用户会使用移动和/或网络应用程序。
考虑身份验证和授权 - 如果您所需要做的就是确定您来自自己的应用程序，那么肯定有更精简的方法。简单的基于证书的解决方案就可以，甚至是基于用户名/密码的解决方案。
但是，如果您希望使用应用程序背后的用户身份来驱动服务的身份验证和授权，那么您确实需要担心用户的身份，当然您可以自己管理，但这就是ACS 非常方便，因为它允许您利用一个或多个现有身份提供商，这使您和用户更轻松。
I think it depends on the specific scenario, you say that users will not access the service dicrecly, but presumably it is the user who will use the mobile and/or web app.
Thinking of authentication and authorisation - if all you need to do is identify that you're coming from your own appilcation, than there are defintiely leaner approaches. simple certificate based solution would do, or even username/password based solution.
If, however, you wish to use the identity of user beheind the app to drive the authentication and authorisation for the service, than you do need to worry about the user's identity, and of course you can manage it yourself, but this is where the ACS comes very handy in that it lets you leverage one or more existing identity providers, which makes it easier for you and the user.
这可能不值得。
ACS 非常适合代表您管理用户身份：换句话说，允许您的用户提出身份声明。
如果您的 Web 服务需要了解用户的身份，那么它绝对值得付出（小的）努力来实现，因为它会为您处理大部分工作。
如果您的 Web 服务不知道用户身份，并且没有为该服务定义外部端点——那么，是的，我也不会为 ACS 操心。
It's probably not worth it.
ACS is great for managing user identity on your behalf: in other words, for allowing your users to make identity claims.
If your Web service needs to know about your users' identities then it's definitely worth the (small) effort to implement, as it takes care of much of the work for you.
If your Web service doesn't know about user identity, and there's no external endpoint defined for the service -- then, yes, I'd not bother with ACS either.