| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
It is possible to have a tenant adopt a storage domain so it can be accessed through the Content Portal if the storage domain is created outside the Content Management API (such as a replication cluster). It is possible to transfer a domain to another existing tenant or have a tenant adopt a storage domain so it can be accessed through the Content Portal if the storage domain is created outside the Content Management API (such as a replication cluster). A special variation to the domain adoption procedure is noted below if that storage domain was created with Swarm's legacy auth/auth.
...
Update the domain to reflect the correct x-tenant-meta-name header, using a COPY method and the &preserve query argument.
This is an example of the commands. The strings {tenant} and {domain} are substituted for the actual tenant and storage domain names.
Use the COPY request to replace the x-tenant-meta-name and retain all other existing metadata.
| Code Block |
|---|
curl -i -X COPY --location-trusted \
-H 'x-tenant-meta-name: {tenant}' \
'http://{storageNode}/?domain={domain}&preserve&replicate=immediate' |
...
The x-tenant-meta-name must match the name of an existing tenant created through the Gateway Management API or Content Portal.
Upon completion of the domain adoption procedure, the storage domain is now subject to the tenant access control policy and root and domain policies. The storage domain switches to using the tenant IDSYS rather than the root IDSYS if the storage domain does not define a separate IDSYS, was previously using the root IDSYS, and the adoptive tenant defines an IDSYS.