Skip to content

Commit 49fd906

Browse files
committed
changes based on Robert's feedback
1 parent 25bd668 commit 49fd906

File tree

3 files changed

+5
-6
lines changed

3 files changed

+5
-6
lines changed

.gitignore

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
21
app/ds_config*
32

43
*/.DS_Store

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ When the token expires, it updates automatically.
130130
### Prerequisites
131131
1. A DocuSign Developer Sandbox account (email and password) on [demo.docusign.net](https://demo.docusign.net).
132132
Create a [free account](https://go.docusign.com/sandbox/productshot/?elqCampaignId=16535).
133-
1. A DocuSign Integration Key (a client ID). To use Authorization code grant, you will need the **Integration Key** itself, and its **secret**. To use Json Web token, you will need the **Integration Key** itself, the **RSA Secret Key** and an API user ID for the user you are impersonating.
133+
1. A DocuSign Integration Key (a client ID). To use Authorization code grant, you will need the **Integration Key** itself, and its **secret**. To use JSON Web token, you will need the **Integration Key** itself, the **RSA Secret Key** and an API user ID for the user you are impersonating.
134134

135135
If you use this example on your own workstation,
136136
the Integration key must include a **Redirect URI** of `http://localhost:5000/ds/callback`
@@ -171,7 +171,7 @@ When the token expires, it updates automatically.
171171
5. Create a new file in your repo source folder named **private.key**, and paste in that copied RSA private key, then save it.
172172
6. Update the file **app/ds_config.py** and include the newly created API key from step 2 as well as your account user id GUID which is also found on the Admin panel: `https://admindemo.docusign.com/api-integrator-key`.
173173

174-
From there you should be able to run the launcher using **python run.py** then selecting **Json Web Token** when authenticaing your account.
174+
From there you should be able to run the launcher using **python run.py** then selecting **JSON Web Token** when authenticaing your account.
175175

176176
#### Payments code example
177177
To use the payments example, create a
@@ -189,7 +189,7 @@ Then add the payment gateway account id to the **app/ds_config.py** file.
189189

190190
### Implicit Grant
191191

192-
The examples in this repository can also be used the
192+
The examples in this repository can also be used with the
193193
Implicit Grant OAuth flow.
194194
See the [Authentication guide](https://developers.docusign.com/esign-rest-api/guides/authentication)
195195
for information on choosing the right authentication flow for your application.

app/ds_config_sample.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@
2929

3030
DS_JWT = {
3131
"ds_client_id": "{CLIENT_ID}",
32-
"ds_impersonated_user_id": "{IMPERSONATED_USER_ID}", # the id of the user
33-
"private_key_file": "./private.key", # create a new file named private.key in the app directory
32+
"ds_impersonated_user_id": "{IMPERSONATED_USER_ID}", # The id of the user.
33+
"private_key_file": "./private.key", # Create a new file in your repo source folder named private.key then copy and paste your RSA private key there and save it.
3434
"authorization_server": "account-d.docusign.com"
3535
}

0 commit comments

Comments
 (0)