From eec0e998afee9f6da315bd2a2f4e2356519bacff Mon Sep 17 00:00:00 2001 From: Stephen Day Date: Fri, 26 Jun 2015 14:14:01 -0700 Subject: [PATCH] Revert "Updates to authentication" Signed-off-by: Stephen J Day --- docs/authentication.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/authentication.md b/docs/authentication.md index e070a0c81..042b2ee21 100644 --- a/docs/authentication.md +++ b/docs/authentication.md @@ -30,11 +30,13 @@ Since the Docker engine uses basic authentication to negotiate access to the Reg While this model gives you the ability to use whatever authentication backend you want through a secondary authentication mechanism implemented inside your proxy, it also requires that you move TLS termination from the Registry to the proxy itself. -Below is a simple example of secured basic authentication (using TLS), using nginx as a proxy. +Below is a simple example of secured basic authentication (using TLS), using nginx as a proxy. -### Requirements +### Requirements -You should have followed entirely the basic [deployment guide](deploying.md). If you have not, please take the time to do so. +You should have followed entirely the basic [deployment guide](deployement.md). + +If you have not, please take the time to do so. At this point, it's assumed that: @@ -169,6 +171,6 @@ Now: This is **advanced**. -You will find [background information here](/spec/auth/token.md), [configuration information here](configuration.md#auth). +You will find [background information here](spec/auth/token.md), [configuration information here](configuration.md#auth). Beware that you will have to implement your own authentication service for this to work (though there exist third-party open-source implementations).