Issue an export content-key challenge
curl --request POST \ --url https://auth.example.com/api/replication-backups/example/exports/example/key-challenges \ --header 'Authorization: Bearer <token>' \ --header 'X-Tenant-Id: example'Requires the grant-specific bearer credential and exact X-Tenant-Id. Every request rechecks expiry, revocation and installed source scope. Only exports created by this grant with the fixed issuer and selection are accessible. Audit persistence is required. Request body must be empty. The client uses RSA-OAEP SHA-256 and the returned context with the existing backup key-envelope protocol; no plaintext passphrase is sent.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Header Parameters
Section titled “Header Parameters ”Must match both the installed source deployment and the grant tenant.
Responses
Section titled “ Responses ”Operation result. Responses are not cacheable.
object
object
object
Example
{ "publicKey": { "kty": "RSA" }}Request rejected; no additional capability is granted.
Request rejected; no additional capability is granted.
Request rejected; no additional capability is granted.
Request rejected; no additional capability is granted.
Request rejected; no additional capability is granted.