英文:
Google App Engine Golang - Register Users Without Google Account
问题
我正在使用Google App Engine构建一个Go(lang)的网站。我希望用户能够通过提供电子邮件和密码来注册网站。我不想使用用户API，因为我不希望我的用户需要一个Google账户，而且我最终计划将其打造成一个付费网站。
在Google App Engine上处理用户注册/身份验证的一个好方法是什么？我应该使用数据存储来存储用户账户和凭据，还是使用Cloud SQL？还有其他好的选择吗？我不知道从哪里开始。
英文:
I'm building a website in Go(lang) using Google App Engine. I want users to be able to register for the site by providing an Email and Password. I don't want to use the users API, because I don't want my users to require a google account and I eventually plan on making this a pay site.
What is a good way to handle user registration/authentication on google app engine? Should I use the datastore for user accounts and credentials, or Cloud SQL? Any other good options? I don't know where to start.
答案1
得分: 3
我认为使用现有的、有声誉的基础设施/服务更容易。
谷歌提供了这样的服务，可以参考https://stackoverflow.com/questions/25442786/what-is-the-difference-between-google-identity-toolkit-google-oaauth-and-google/31053422#31053422。
我选择了Google Identity Toolkit，它很好地支持同时使用私有账户和多个流行身份提供商的联合登录。
更新于2016年6月17日：GITkit文档认证的横幅表明GITkit可能会被整合到Firebase Authentication中。
英文:
IMHO it's easier to use an existing, reputable infrastructure/service.
Google offers such services, see https://stackoverflow.com/questions/25442786/what-is-the-difference-between-google-identity-toolkit-google-oaauth-and-google/31053422#31053422.
I opted for the Google Identity Toolkit, which nicely supports simultaneously both private accounts and federated logins with several popular identity providers.
Update June 17, 2016: The banner on the GITkit doumentation authentication indicates GITkit may be on its way out, to be absorbed into the Firebase Authentication.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论