Migrating oauth2 Tokens - Embedded Edition

Migrating oauth2 Tokens: Offline Mode

Procedure

To export oauth2 tokens from Local Edition 4.x.x to 6.x.x, run the following command:
```
migrate.py --export_tokens
```
- This command continues to run until all tokens have been migrated. It outputs progress in the terminal and remembers its progress in the file tokens.offset.
- If the command is interrupted, you can restart it, and token migration will resume after the restart.
- You can start this command at any time. After restarting, it searches for new tokens in Local Edition 4.x.x and migrates them to Local Edition 6.x.x.
To import oauth2 tokens to 6.x.x, run the following command:
```
./migrate.py --import_tokens
```
Token imports may take longer to finish due to disconnecting from the terminal. To prevent interruption, run the following screen command:
```
screen ./migrate.py --import_tokens
```
If it still remains disconnected from the terminal, log in to a terminal and run the following command to import token import.
```
screen -r
```

Migrating oauth2 Tokens: Online Mode

To migrate oauth2 tokens from Boomi Cloud API Management – Local Edition 4.x.x to Boomi Cloud API Management – Local Edition 6.x.x, run the following command:

./migrate.py --migrate_tokens

This command continues to run until all tokens have been migrated. It outputs progress in the terminal and remembers its progress in the file tokens.offset.
If the command is interrupted, you can restart it, and token migration will resume after the restart.
You can start this command at any time. After restarting, it searches for new tokens in Boomi Cloud API Management – Local Edition 4.x.x and migrates them to Boomi Cloud API Management – Local Edition 6.x.x.

note

The online mode in the embedded edition may not be able to communicate securely with the MySQL service used by Local Edition 6.x.x. In such a situation, the offline mode in the embedded edition can be used to migrate tokens.