Updated Upgrading 1.0 to 1.1 (markdown)
parent
b5b76c48c0
commit
043325f91e
|
@ -20,3 +20,11 @@ If you are running the server with a persistent database store, you will need to
|
|||
Due to an upstream library change, existing authorizations are incompatible between 1.0 and 1.1. This effectively means that **all active access tokens must be revoked** (or translated using some form of external process) during the upgrade process. Note that this includes any **Registration Access Tokens** used for dynamically registered clients.
|
||||
|
||||
Otherwise, all authorization grants, clients, whitelists, blacklists, and scopes may remain in place following the instructions above.
|
||||
|
||||
## Data Import/Export
|
||||
|
||||
As of version **1.0.17**, there is an admin-accessible API that can export data from a running system. To access this API, log in as an administrator and send a `GET` request to `/api/data` to return the JSON object representing the server's current state. **NOTE WELL:** this export includes information including tokens, authentication objects, client secrets, and other sensitive security information.
|
||||
|
||||
To re-import this data, log in as an administrator on a newly-installed server and send a `POST` request to `/api/data` with a content type of `application/json` and the fully-formed JSON document exported from the API. This import MUST be done on an empty database with full schema or else you risk newly imported objects conflicting with existing objects.
|
||||
|
||||
A version of the import/export API is currently in the works for the 1.1 branch, which will allow for import of 1.0 data into the 1.1 database.
|
Loading…
Reference in New Issue