Skip to content
This repository was archived by the owner on Nov 30, 2023. It is now read-only.

update to oauth section #68

Open
CrystalOnScript wants to merge 4 commits into
base: master
Choose a base branch
from
Open

update to oauth section #68

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8f64d12
update to oauth section
Jun 9, 2018
46aed3d
added deprecation warning and removed licensing api infromation from …
Jun 15, 2018
ecf0fee
removed images
Jun 15, 2018
97e1f68
language nit and fixed links
Jun 15, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions get_started.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
{{+bindTo:partials.standard_store_article}}

<h1>Tutorial: Licensing API</h1>

<p class="caution">
<b>Important:</b>
Chrome will be removing support for Chrome Apps on Windows, Mac, and
Linux. Chrome OS will continue to support Chrome Apps. Additionally,
Chrome and the Web Store will continue to support extensions on all
platforms.
<a href="http://blog.chromium.org/2016/08/from-chrome-apps-to-web.html">
Read the announcement</a> and learn more about
<a href="https://developers.chrome.com/apps/migration">
migrating your app</a>.
Hosted Apps are no longer supported.
For payment information refer to
<a href="one_time_payments.html">One-Time Payments</a>,
<a href="payments-iap.html">
In-App Payments with Payments Merchant Account and the Chrome Web Store API
</a> and
<a href="money.html">Monetizing Your Chrome Web Store Item</a>.
</p>

<h1>Tutorial: Licensing API</h1>

<p>
This tutorial walks you through
creating an app that uses the Chrome Web Store Licensing API.
Expand Down
94 changes: 3 additions & 91 deletions overview.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,15 +171,6 @@ <h2 id="charging"> Charging for your app </h2>
<li> <b>Custom payment solution</b> </li>
</ol>

<p class="caution">
<b>Note</b>:
Although packaged apps and extensions
can use Chrome Web Store Payments,
it's difficult for them to use the Licensing API securely.
Themes have no executable code,
so they can't use the Licensing API.
</p>

<h3 id="freevnot"> Providing some functionality for free </h3>

<p>
Expand Down Expand Up @@ -288,16 +279,6 @@ <h2 id="webstore"> Uploading and publishing your item </h2>
For details, see <a href="publish.html">Publishing Your App</a>.
</p>

<p class="note">
<b>Note</b>:
Before you publish your first app,
you must pay a $5 developer signup fee.
If you used the Chrome Developer Dashboard before {{ grandfatherdate }}&mdash;to
publish an extension, for example&mdash;you
don't need to pay the fee.
</p>


<p class="backtotop"><a href="#top">Back to top</a></p>
<h2 id="drm"> Protecting your item from unauthorized use </h2>

Expand All @@ -319,55 +300,6 @@ <h2 id="drm"> Protecting your item from unauthorized use </h2>
being served by the Chrome Web Store.
</p>


<h3 id="licensingapi"> Using the Licensing API to check for payment </h3>

<p>
The Chrome Web Store Licensing API lets you find out
whether the current user has paid for your item
using Chrome Web Store Payments.
To use the Licensing API,
you need two IDs and an OAuth access token:
</p>

<dl>
<dt> App ID </dt>
<dd>
The Chrome Developer Dashboard generates this ID
the first time you upload the app.
You can get it from the Chrome Developer Dashboard's
page for your item.
</dd>

<dt> User ID </dt>
<dd>
Your app needs to get a Google Account identity for the user,
using OpenID.
</dd>

<dt> OAuth access token </dt>
<dd>
After you upload your app,
you can ask the Chrome Developer Dashboard
to generate an OAuth access token and secret.
</dd>
</dl>

<p>
Once you have these items,
you can make requests to the license server
using OAuth and the Licensing API.
The license server tells you whether the user has access to this item,
and whether a free trial is in effect.
Rather than query the server repeatedly,
you should cache the response.
</p>

<p>
For detailed instructions on using the Licensing API, see
<a href="payments-iap.html">Checking for Payment</a>.
</p>

<h3 id="recommendations">Encouraging payment</h3>

<p>
Expand Down Expand Up @@ -400,40 +332,20 @@ <h3 id="recommendations">Encouraging payment</h3>
<h2 id="next">What next?</h2>

<p>
Here are some choices for where to go next:
Publish your first item in the Chrome Web Store by following the
<a href="get_started_simple.html">Getting Started Tutorial</a>.
</p>

<dl>
<dt> <a href="get_started_simple.html">Tutorial: Getting Started</a> </dt>
<dd> Publish your first item in the Chrome Web Store.
</dd>

<dt> <a href="check_for_payment.html">Checking for Payment</a> </dt>
<dd> Learn how to use the Licensing API to
check whether the user has paid for your item.
</dd>

<dt> <a href="get_started.html">Tutorial: Licensing API</a> </dt>
<dd> Write an app that uses the Licensing API.
</dd>

<dt> <a href="samples.html">Samples</a> </dt>
<dd> Find samples in multiple languages of apps
that use the Licensing API.
</dd>

</dl>

<p>
If you just want to write your item,
see the developer doc for the type of app you're interested in:
</p>

<ul>

<li> <a href="/extensions/index.html">Chrome Extensions</a> </li>
<li> <a href="/apps/about_apps.html">Chrome Apps</a> </li>
<li> <a href="/extensions/themes.html">Themes</a> </li>
<li> <a href="/extensions/index.html">Chrome Extensions</a> </li>
</ul>

<p class="backtotop"><a href="#top">Back to top</a></p>
Expand Down