Migration Overview Index
This guide covers several different migration pathways, which differ based on the encryption method that a client can use to connect to Thredd. The migration process that you must follow depends on your existing configuration with Thredd and your target configuration state.
There is a Migration Overview for each typical migration pathway, which summarises the different stages of the migration process. Use the Migration Overview as your guide to work through the different stages, and use the links within it to the instructions you must complete for each stage.
To ensure that you follow the correct process, refer to the Migration Overview that matches your target state for connecting to Thredd. You should also familiarise yourself with the Thredd Secure Framework and Thredd Portal overview.
Note that in the following table:
-
Existing setups: Raidiam Connect (Certificate Authority) and Cloudentity are responsible for Identity and Access Management (IAM).
-
Target setups: Thredd Portal is responsible for Identity and Access Management (IAM).
|
Existing setup |
Target setup |
Relevant Migration Overview and additional pages |
|---|---|---|
|
Mutual TLS with:
|
Mutual TLS with:
|
Migrating from mTLS to a new mTLS connection to Thredd, REST APIs and API Hub |
|
Mutual TLS with:
|
Mutual TLS with:
|
Migrating from mTLS to a new mTLS connection to Thredd, REST APIs and API Hub and |
|
Mutual TLS with:
|
Mutual TLS with:
|
Migrating from mTLS to a new mTLS connection to Thredd, REST APIs, API Hub and SOAP Web Services and |
|
Mutual TLS with:
|
Mutual TLS with:
|
Migrating from mTLS to a new mTLS connection to Thredd and SOAP Web Services only |
|
Mutual TLS with:
|
Mutual TLS with:
|
Migrating from mTLS to a new mTLS connection to Thredd and SOAP Web Services only and |
For the latest technical documentation, see the Documentation Portal.