diff --git a/CHANGELOG.md b/CHANGELOG.md
index c14aa941edb..f5afd3b5352 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,8 @@ All of the packages in the `apollo-server` repo are released with the same versi
 
 ### vNEXT
 
+- Update link inside Authentication Docs [PR #1682](https://github.com/apollographql/apollo-server/pull/1682)
+
 ### v2.0.8
 
 - Reporting: Catch Error if JSON.Stringify Fails for Engine Trace [PR #1668](https://github.com/apollographql/apollo-server/pull/1668)
diff --git a/docs/source/best-practices/authentication.md b/docs/source/best-practices/authentication.md
index 5b826230ea4..ddc335b1760 100644
--- a/docs/source/best-practices/authentication.md
+++ b/docs/source/best-practices/authentication.md
@@ -21,7 +21,7 @@ GraphQL offers similar authentication and authorization mechanics as REST and ot
 
 <h2>Authenticating users</h2>
 
-All of the approaches require that users be authenticated with the server. If our system already has login method setup to authenticate users and provide credentials that can be used in subsequent requests, we can use this same system to authenticate GraphQL requests. With that said, if we are creating a new infrastructure for user authentication, we can follow the existing best practice to authenticate users. For a full example of authentication, follow [this example](), which uses [passport.js](http://www.passportjs.org/).
+All of the approaches require that users be authenticated with the server. If our system already has login method setup to authenticate users and provide credentials that can be used in subsequent requests, we can use this same system to authenticate GraphQL requests. With that said, if we are creating a new infrastructure for user authentication, we can follow the existing best practice to authenticate users. For a full example of authentication, follow [this example](#auth-example), which uses [passport.js](http://www.passportjs.org/).
 
 <h2>Schema Authorization</h2>