|
a/Allura/docs/migration.rst |
|
b/Allura/docs/migration.rst |
|
... |
|
... |
| 91 |
existing API tickets (most recently generated first) below it. To create a ticket,
|
91 |
existing API tickets (most recently generated first) below it. To create a ticket,
|
| 92 |
fill in following information:
|
92 |
fill in following information:
|
| 93 |
|
93 |
|
| 94 |
* Username - all actions performed using the ticket will be tied to this account.
|
94 |
* Username - all actions performed using the ticket will be tied to this account.
|
| 95 |
* Capabilities (JSON) - all API tickets must have capabilities (represented with
|
95 |
* Capabilities (JSON) - all API tickets must have capabilities (represented with
|
| 96 |
JSON dictionary) set. For import, this should be ``{"import": <projectname>}``,
|
96 |
JSON dictionary) set. For import, this should be ``{"import": [<nbhd_name>, <project_shortname>}``,
|
| 97 |
e.g. ``{"import": "test"}``. For multiple projects, several tickets must be created.
|
97 |
e.g. ``{"import": ["Projects", "test"]}``. For multiple projects, several tickets must be created.
|
| 98 |
* Expiration date - All API tickets are time-limited, with default active duration
|
98 |
* Expiration date - All API tickets are time-limited, with default active duration
|
| 99 |
of 48 hours, all actions using the ticket must be performed within this timeframe.
|
99 |
of 48 hours, all actions using the ticket must be performed within this timeframe.
|
| 100 |
|
100 |
|
| 101 |
Once a ticket is generated (will be shown topmost in the list), API ticket and secret
|
101 |
Once a ticket is generated (will be shown topmost in the list), API ticket and secret
|
| 102 |
key values must be passed securely to the requesting user.
|
102 |
key values must be passed securely to the requesting user.
|