From ebeaf8fd57eae7b0ec7bed6c730d2ea410785281 Mon Sep 17 00:00:00 2001 From: tmauro-nginx Date: Mon, 22 Jun 2015 11:42:06 -0700 Subject: [PATCH] Update README.md Standardizing representation of hyperlink to "How Authentication Works in the Reference Implementation" section of blog post. Adding space in front of OpenLDAP hyperlink in 'Compatibility' section, hoping that makes the link look right. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ed2dd09..f2e060a 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ The ldap-auth daemon, which mediates between NGINX Plus and the LDAP server, is ![NGINX LDAP Architecture](http://nginx.wpengine.com/wp-content/uploads/2015/06/components-e1434577427617.jpg) -For a step-by-step description of the authentication process in the reference implementation, see [NGINX Plus and NGINX Can Authenticate Application Users](https://nginx.com/blog/nginx-plus-authenticate-users#ldap-auth-flow). +For a step-by-step description of the authentication process in the reference implementation, see [How Authentication Works in the Reference Implementation](https://nginx.com/blog/nginx-plus-authenticate-users#ldap-auth-flow) in [NGINX Plus and NGINX Can Authenticate Application Users](https://nginx.com/blog/nginx-plus-authenticate-users). ## Installation and Configuration @@ -142,7 +142,7 @@ To modify the ldap-auth daemon to communicate with a different (non-LDAP) type o The auth daemon was tested against default configurations of the following LDAP servers: