Issue a backup key challenge
curl --request POST \ --url https://auth.example.com/api/admin/tenant-backups/example/key-challenges \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "inputId": "example" }'Requires backup read, manage, the operation-specific export or import permission, and a human Admin session with fresh MFA (five minutes). The caller must be the operation creator and the operation must be queued or waiting. Import operations require one challenge per inputId; export operations use an empty body. Returns an RSA-OAEP SHA-256 public JWK and the exact binding context. The client wraps its content key with the operation key handoff format; it must never send its passphrase. submitExpiresAt and context.expiresAt are epoch milliseconds. The submission window is ten minutes and accepted keys expire after 24 hours.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Request Body
Section titled “Request Body ”object
Example generated
{ "inputId": "example"}Responses
Section titled “ Responses ”Issue a backup key challenge
object
object
object
Example
{ "publicKey": { "kty": "RSA" }}The request was rejected. No key material is returned.
object
Example generated
{ "error": "example"}The request was rejected. No key material is returned.
object
Example generated
{ "error": "example"}The request was rejected. No key material is returned.
object
Example generated
{ "error": "example"}The request was rejected. No key material is returned.
object
Example generated
{ "error": "example"}The request was rejected. No key material is returned.
object
Example generated
{ "error": "example"}