JavaLeaks
diff --git a/‎content/v3/enterprise.md‎
Lines changed: 9 additions & 10 deletions b/‎content/v3/enterprise.md‎
Lines changed: 9 additions & 10 deletions
diff --git a/‎content/v3/enterprise/management_console.md‎
Lines changed: 4 additions & 9 deletions b/‎content/v3/enterprise/management_console.md‎
Lines changed: 4 additions & 9 deletions
@@ -15,12 +15,6 @@ GitHub Enterprise supports the same powerful API available on GitHub.com as well
 - Use the [Management Console][] API to perform common administrative tasks
 - Use the [User Administration][] API to promote, demote, suspend, and unsuspend users
 
-[Admin Stats]: admin_stats/
-[License]: license/
-[Search Indexing]: search_indexing/
-[Management Console]: management_console/
-[User Administration]: /v3/users/administration/
-
 ## Endpoint URLs
 
 All API endpoints—except [Management Console][] API endpoints—are prefixed with the following URL:
@@ -39,12 +33,17 @@ http(s)://<em>hostname</em>/
 
 Your Enterprise installation's API endpoints accept [the same authentication methods](http://developer.github.com/v3/#authentication) as the GitHub.com API. Specifically, you can authenticate yourself with **[OAuth tokens][]** (which can be created using the [Authorizations API][]) or **[basic authentication][]**.
 
-[OAuth tokens]: /v3/oauth/
-[basic authentication]: /v3/#basic-authentication
-
-The [Admin Stats][], [License][], [Search Indexing][], and [User Administration][] API endpoints are only accessible to GitHub Enterprise site administrators. The [Management Console][] API endpoints are only accessible with a valid license file.
+The [Admin Stats][], [License][], [Search Indexing][], and [User Administration][] API endpoints are only accessible to GitHub Enterprise site administrators. The [Management Console][] API endpoints are only accessible via the [Management Console password][].
 
 [Authorizations API]: /v3/oauth_authorizations/#create-a-new-authorization
+[OAuth tokens]: /v3/oauth/
+[basic authentication]: /v3/#basic-authentication
+[Admin Stats]: admin_stats/
+[License]: license/
+[Search Indexing]: search_indexing/
+[Management Console]: management_console/
+[User Administration]: /v3/users/administration/
+[Management Console password]: https://enterprise.github.com/help/articles/setting-the-management-console-password
 
 ## Past Releases
 
 
@@ -11,23 +11,18 @@ The Management Console API helps you manage your GitHub Enterprise installation.
 
 ## Authentication
 
-You need to pass [an MD5 hash](https://en.wikipedia.org/wiki/MD5#MD5_hashes) of your license file as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#upload-a-license-and-software-package-for-the-first-time). On most systems, you can get this hash by simply calling `md5sum` on the license file:
+You need to pass your [Management Console password](https://enterprise.github.com/help/articles/setting-the-management-console-password) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#upload-a-license-and-software-package-for-the-first-time).
 
-<pre class="terminal">
-$ md5sum github-enterprise.ghl
-5d10ffffa442a336061daee294536234  github-enterprise.ghl
-</pre>
-
-You can use the `license_md5` parameter to send this token with each request. For example:
+Use the `api_key` parameter to send this token with each request. For example:
 
 <pre class="terminal">
-$ curl 'http://<em>hostname</em>/setup/api?license_md5=<em>md5-checksum-of-license</em>'
+$ curl 'http://<em>hostname</em>/setup/api?api_key=<em>your-amazing-password</em>'
 </pre>
 
 You can also use standard HTTP authentication to send this token. For example:
 
 <pre class="terminal">
-$ curl 'http://license:<em>md5-checksum-of-license</em>@<em>hostname</em>/setup/api'
+$ curl 'http://api_key:<em>your-amazing-password</em>@<em>hostname</em>/setup/api'
 </pre>
 
 ## Upload a license and software package for the first time