'Get Client ID' section in the identity API docs has been updated

chrome/common/extensions/docs/templates/articles/app_identity.html

 <h1>Identify User</h1>
 
 
 <p>
 Web authentication protocols utilize HTTP features,
 but packaged apps run inside the app container;
 they don’t load over HTTP and can’t perform redirects or set cookies.
 </p>
 
 <p>
@@ skipping 68 matching lines @@
 
 <p>
 You need to copy the key in the installed
 <code>manifest.json</code> to your source manifest.
 This ensures that the key isn't overridden anytime your reload your app
 or share the app with other users.
 It's not the most graceful task, but here's how it goes:
 </p>
 
 <ol>
-        <li>Go to your
-                <a href="http://www.chromium.org/user-experience/user-data-directory">user data directory</a>.
-                Example on MacOs: <code>~/Library/Application\ Support/Google/Chrome/Default/Extensions</code></li>
-        <li>List the installed apps and extensions and match your app ID on the apps and extensions management page
-                to the same ID here.</li>
+        <li>Go to your <a href="http://www.chromium.org/user-experience/user-data-directory">user data directory</a>.
+        Example on MacOs:
+        <code>~/Library/Application\ Support/Google/Chrome/Default/Extensions</code></li>
+        <li>List the installed apps and extensions and match your app ID on the apps and extensions management page to the same ID here.</li>
         <li>Go to the installed app directory (this will be a version within the app ID).
-                Open the installed <code>manifest.json</code>
-                (pico is a quick way to open the file).</li>
+        Open the installed <code>manifest.json</code>
+        (pico is a quick way to open the file).</li>
         <li>Copy the "key" in the installed <code>manifest.json</code> and paste it into your app's source manifest file.</li>
 </ol>
 
 <h3 id="client_id">Get your client ID</h3>
 
 <p>
-Setting up the client ID is currently not available externally
-via <a href="https://devconsole-canary.corp.google.com/apis/">Google APIs Console</a>.
-So to setup the OAuth2 client ID,
-email <a href="mailto:chrome-apps-auth-requests@google.com">chrome-apps-auth-request@google.com</a>
-with your stable app ID and
-we will reply appropriately with your OAuth2 client ID.
+You need to register your app
+in the Google APIs Console
+to get the client ID:
 </p>
+ 
+<ol>
+        <li> Login to the <a href="https://code.google.com/apis/console/">Google APIs Console</a>
+        using the same Google account used to upload your app. </li>

[Munjal (Google), 2013/01/04 19:48:05]

used to upload your app to Chrome Web Store.

[mkearney1, 2013/01/07 22:02:58]

Done.

+        <li>Create a new project by expanding the drop-down menu in the top-left
+        corner and selecting the <strong>Create...</strong> menu item. </li>
+        <li> Once created and named,
+    go to the "Services" navigation menu item and
+    turn on any Google services your app needs. </li>
+    <li> Go to the "API Access" navigation menu item and click on the
+    <strong>Create an OAuth 2.0 client ID...</strong> blue button. </li>
+    <li> Enter the requested branding information,
+    select the <strong>Installed application</strong> type. </li>
+    <li> Select <strong>Chrome Application</strong> and
+    enter your application ID
+    (same ID displayed in the apps and extensions management page). </li>

[Munjal (Google), 2013/01/04 19:48:05]

We should add a note somewhere on this page that if the ID here does not match
the app id from which the getAuthToken call is done, an error will occur.

I think it is important to mention this since this is the most common error I
have seen so far from developers using the identity API.

[mkearney1, 2013/01/07 22:02:58]

Done.

+  </ol>
 
 <h3 id="update_manifest">Update your manifest</h3>
 
 <p>
 You need to update your manifest to include
 the client ID and scopes.
 Here's the sample "oauth2" for the
 <a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/gdocs">gdocs sample</a>:
 </p>
 
@@ skipping 120 matching lines @@
 </p>
 
 <p>
 The best practice we suggest is to use silent mode
 when there is no user gesture involved and use interactive mode
 if there is a user gesture (for example, the user clicked the Sign In button in your app).
 Note that we do not enforce gesture requirement.
 </p>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>