Skip to content

Commit 1fc75e4

Browse files
Rob BlackburnRob Blackburn
authored andcommitted
removing the sandbox credentials
1 parent 63a57ff commit 1fc75e4

32 files changed

+1216
-265
lines changed

.DS_Store

0 Bytes
Binary file not shown.

docs/get.md

Lines changed: 12 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -31,14 +31,12 @@ If you've ever signed into a site using Google or Facebook instead of your crede
3131
###Get API credentials
3232
API credentials consisting of a **client ID** and a **client secret** are needed in order to get Authenticated iDs and/or user permissions.
3333

34-
To get Authenticated iDs, you can use Public or Member API credentials. To get permission to read non-public information or add/update researchers' ORCID records, you'll need Member API credentials. To request API credentials, see [Request API credentials](https://orcid.org/content/register-client-application)
34+
To get Authenticated iDs, you can use Public or Member API credentials. To get permission to read non-public information or add/update researchers' ORCID records, you'll need Member API credentials.
3535

36-
For this tutorial, we'll use a set of demo credentials:
36+
For this tutorial, please use your own sandbox API credentials:
37+
38+
To request API credentials, see [Request API credentials](https://orcid.org/content/register-client-application)
3739

38-
```
39-
client_id: APP-XA6KUTFCVQL0622C
40-
client_secret: 7c8d6b1b-401b-4f5d-9b8b-b8108c6e197c
41-
```
4240
(Demo client secret created for this tutorial - do not share API client secrets!)
4341

4442

@@ -54,21 +52,21 @@ To kick off the OAuth process, we'll need to create a special authorization URL
5452

5553
| Parameter | Description | Example |
5654
| ----------| ----------- | ------- |
57-
|**client_id**| Your Member or Public API client ID (issued by ORCID)<br>To request API credentials, see [Request API credentials](https://orcid.org/content/register-client-application) | ```APP-XA6KUTFCVQL0622C``` |
55+
|**client_id**| Your Member or Public API client ID (issued by ORCID)<br>To request API credentials, see [Request API credentials](https://orcid.org/content/register-client-application) | ```[APP-*****************]``` |
5856
|**response_type**| | ```code``` |
5957
|**scope**| API action(s) you want to request permission for, from the list of [ORCID Scopes](https://members.orcid.org/api/oauth/orcid-scopes). | ```/authorize``` <br> ```/activities/update```
6058
|**redirect_uri**| Page on your site that users will see after they complete the authorization process (must be on the list of allowed redirect URIs you specified when requesting your API credentials) | ```https://developers.google.com/oauthplayground``` |
6159

62-
To request permission to add/update activities (affiliations, funding, works, peer review items) using a demo client ID created for this tutorial, our authorization URL will be:
63-
60+
To request permission to add/update activities (affiliations, funding, works, peer review items), our authorization URL will be:
61+
Enter you own client ID where it says [APP-*****************]
6462
```
65-
https://sandbox.orcid.org/oauth/authorize?client_id=APP-XA6KUTFCVQL0622C&response_type=code&scope=/read-limited&redirect_uri=https://developers.google.com/oauthplayground
63+
https://sandbox.orcid.org/oauth/authorize?client_id=[APP-****************]&response_type=code&scope=/read-limited%20/activities/update%20/person/update&redirect_uri=https://developers.google.com/oauthplayground
6664
```
6765

6866
###Get an authorization Code
6967

70-
1. In a new window or tab, visit<br>
71-
[https://sandbox.orcid.org/oauth/authorize?client_id=APP-XA6KUTFCVQL0622C&response_type=code&scope=/read-limited&redirect_uri=https://developers.google.com/oauthplayground](https://sandbox.orcid.org/oauth/authorize?client_id=APP-XA6KUTFCVQL0622C&response_type=code&scope=/read-limited&redirect_uri=https://developers.google.com/oauthplayground)
68+
1. In a new window or tab, visit remebering to fill in your own APP<br>
69+
[https://sandbox.orcid.org/oauth/authorize?client_id=[APP-*****************]&response_type=code&scope=/read-limited&redirect_uri=https://developers.google.com/oauthplayground](https://sandbox.orcid.org/oauth/authorize?client_id=[APP-*****************]&response_type=code&scope=/read-limited%20/activities/update%20/person/update&redirect_uri=https://developers.google.com/oauthplayground)
7270

7371
2. An ORCID sign-in screen listing the requested permissions will appear; sign into your Sandbox account and click **Authorize**<br>
7472
<img src="../images/04-2_oauth-screen.png" width="400" alt="ORCID OAuth sign-in screen" />
@@ -92,8 +90,8 @@ In a real-world situation, this exchange would be done by your system, using a p
9290
|**Authorization endpoint**| ```https://sandbox.orcid.org/oauth/authorize``` |
9391
|**Token endpoint**| ```https://sandbox.orcid.org/oauth/token``` |
9492
|**Access token location**| Authorization header w/Bearer prefix |
95-
|**OAuth Client ID**| ```APP-XA6KUTFCVQL0622C```<br>(Demo client ID created for this tutorial) |
96-
|**OAuth Client Secret**| ```7c8d6b1b-401b-4f5d-9b8b-b8108c6e197c```<br>(Demo client secret created for this tutorial - do not share API client secrets!) |
93+
|**OAuth Client ID**| ```[APP-*****************]```<br>(Demo client ID created for this tutorial) |
94+
|**OAuth Client Secret**| ```0000000-0000-0000-0000-000000000000```<br>(Your own client secret created earlier - do not share API client secrets!) |
9795

9896
3. In the **Step 2 Exchange authorization code for tokens** section at left, click **Exchange authorization code for tokens**<br>
9997
<img src="../images/04-3_exchange-code.png" width="400" alt="Google OAuth Playground exchanging authorization code for access token" />

site/404.html

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -202,8 +202,8 @@
202202

203203

204204
<li class="md-nav__item">
205-
<a href="/search/" title="4. SEARCH&#58; public info" class="md-nav__link">
206-
4. SEARCH&#58; public info
205+
<a href="/get/" title="4. GET&#58; authenticated iDs &amp; permission" class="md-nav__link">
206+
4. GET&#58; authenticated iDs &amp; permission
207207
</a>
208208
</li>
209209

@@ -214,8 +214,8 @@
214214

215215

216216
<li class="md-nav__item">
217-
<a href="/collect/" title="5. GET&#58; authenticated iDs &amp; permission" class="md-nav__link">
218-
5. GET&#58; authenticated iDs &amp; permission
217+
<a href="/post/" title="5. POST&#58; an affiliation" class="md-nav__link">
218+
5. POST&#58; an affiliation
219219
</a>
220220
</li>
221221

@@ -226,8 +226,8 @@
226226

227227

228228
<li class="md-nav__item">
229-
<a href="/connect/" title="6. POST&#58; an affiliation" class="md-nav__link">
230-
6. POST&#58; an affiliation
229+
<a href="/put/" title="6. PUT&#58; Update an affiliation" class="md-nav__link">
230+
6. PUT&#58; Update an affiliation
231231
</a>
232232
</li>
233233

@@ -238,8 +238,8 @@
238238

239239

240240
<li class="md-nav__item">
241-
<a href="/sync/" title="7. PUT&#58; Update an affiliation" class="md-nav__link">
242-
7. PUT&#58; Update an affiliation
241+
<a href="/display/" title="7. DISPLAY&#58; Presenting ORCID in your system" class="md-nav__link">
242+
7. DISPLAY&#58; Presenting ORCID in your system
243243
</a>
244244
</li>
245245

@@ -250,8 +250,8 @@
250250

251251

252252
<li class="md-nav__item">
253-
<a href="/display/" title="8. DISPLAY&#58; Presenting ORCID in your system" class="md-nav__link">
254-
8. DISPLAY&#58; Presenting ORCID in your system
253+
<a href="/search/" title="8. SEARCH&#58; public info" class="md-nav__link">
254+
8. SEARCH&#58; public info
255255
</a>
256256
</li>
257257

0 commit comments

Comments
 (0)