Google App Engine的用户API太严格了？ [英] User API for Google App Engine far too restrictive?

问题描述

看看Google App Engine API，看起来尽管它有很多优秀的功能，但用户API非常有限。您似乎只能验证拥有Google帐户的人，或使用OpenID帐户，或通过某些OAuth功夫（与Facebook帐户握手等）。

似乎是任何想通过在应用程序中创建用户帐户来获得专有用户基础的人的主要障碍。简而言之，我不希望我的用户必须使用或创建Google帐户才能访问我的应用。

是否有其他人遇到此限制，并且已经一个使用GAE的交易断路器？我错过了什么吗？有可能在应用程序中部署我自己的基于Spring的安全等，并使用我自己的用户API？对此问题的评论非常感谢。感谢。

解决方案

您可以完全忽略Users API并实现您自己的身份验证系统，就像您在其他任何人托管环境。没有任何关于App Engine的信息可以阻止您这么做。

用户API只是为了方便用户，如果您想省去重新实施的努力一切，并且让用户不必填写另一个注册表单并记住另一组凭证。

Looking at the Google App Engine API, it seems that despite all its great features, the User API is extremely limiting. It seems you can only authenticate people who have a Google account, or use an OpenID account, or via some OAuth kung fu (handshaking with a Facebook account etc).

This appears to be a major stumbling block for anyone who wants a proprietary user base by creating user accounts within the application. In short, I don't want my users to have to use or create a Google account to access my app.

Has anyone else come across this limitation and has it been a deal breaker for using the GAE? Am I missing something? It is possible to deploy my own Spring based security etc within the app and use my own User API? Comments on this issue greatly appreciated. Thanks.

解决方案

You're free to completely ignore the Users API and implement your own authentication system, as you would in any other hosting environment. Nothing about App Engine prevents you from doing so.

The Users API is just there as a convenience, in case you'd like to spare yourself the effort of re-implementing everything, and spare your users the inconvenience of filling out another sign up form and remembering another set of credentials.

这篇关于Google App Engine的用户API太严格了？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！