From 5dce563e49401b161e89c24db64605714a153841 Mon Sep 17 00:00:00 2001 From: Anchor Date: Fri, 20 Feb 2015 23:50:02 -0800 Subject: [PATCH] Fix intro to section 14.4.md --- en/14.4.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/en/14.4.md b/en/14.4.md index 4d2fc8f0..dd5e2404 100644 --- a/en/14.4.md +++ b/en/14.4.md @@ -1,12 +1,12 @@ # 14.4 User validation -In the process of developing Web applications, user authentication is frequently encountered problems developers, user log in, registration, log out and other operations, and the general certification is also divided into three aspects of certification +In the process of developping web applications, user authentication is a problem which developers frequently encounter. User login, registration and logout, among other operations, as well as general authentication can also divided into three parts: -- HTTP Basic and HTTP Digest Authentication -- Third Party Certified Integration: QQ, micro-blogging, watercress, OPENID, Google, GitHub, Facebook and twitter, etc. -- Custom user log in, registration, log out, are generally based on session, cookie authentication +- HTTP Basic, and HTTP Digest Authentication +- Third Party Authentication Integration: QQ, micro-blogging, watercress, OPENID, Google, GitHub, Facebook and twitter, etc. +- Custom user login, registration, logout, are generally based on sessions and cookie authentication -beego There is no way for any of these three forms of integration, but can make use of third party open source library to achieve the above three methods of user authentication, but the first two subsequent authentication beego be gradually integrated. +Beego does not natively provide support for any of these three things, however you can easily make use of existing third party open source libraries to implement them. The first two authentication solutions are on Beego's roadmap to eventually be integrated. ## HTTP basic and digest authentication