|
1 | | -# To fetch below information do login to Sign console then click on Adobe Sign API tab |
2 | | -# in API information tab click on Integration Key to 'Create integration key' after selecting appropriate 'scope' |
| 1 | +# This is the Sign connector config file template |
| 2 | +# For more information, see https://adobe-apiplatform.github.io/user-sync.py/en/user-manual/sign_sync.html#sign-connector-config |
| 3 | + |
| 4 | +# --- API Access Options --- |
| 5 | +# Options to configure Sign API access |
| 6 | +# See https://adobe-apiplatform.github.io/user-sync.py/en/user-manual/sign_sync.html#sign-connector-config |
3 | 7 | host: api.echosign.com |
4 | 8 | integration_key: [Sign API Key] |
5 | 9 | admin_email: user@example.com |
6 | | -# Flag to (dis)allow creation of new users in the Sign Neptune Console |
| 10 | + |
| 11 | +# --- Target-specific Behavior Options --- |
| 12 | +# Options to govern target behavior |
7 | 13 | create_users: False |
8 | | -# Flag to (dis)allow deactivation of users in the Sign Neptune Console |
9 | 14 | deactivate_users: False |
10 | 15 |
|
11 | | -# (optional) You can store credentials in the operating system credential store |
12 | | -# (Windows Credential Manager, Mac Keychain, Linux Freedesktop Secret Service |
13 | | -# or KWallet - these will be built into the Linux distribution). |
14 | | -# To use this feature, uncomment the following entry and remove the |
15 | | -# key entry above. |
16 | | -# The actual credential value are placed in the credential store with the |
17 | | -# username as the admin_email field value, and the key name (perhaps called internet |
18 | | -# or network address) as the value below. |
| 16 | +# Instead of storing API key in plaintext, store in OS credential keychain |
| 17 | +# See https://adobe-apiplatform.github.io/user-sync.py/en/user-manual/sign_sync.html#securing-the-api-key |
19 | 18 | #secure_integration_key_key: sign_key |
0 commit comments