Ed25519 - Refresh a key using your share
POST/ed25519/refresh
Used for refreshing the secret material of all parties without altering the public key at all.
Returns a new key_id
for the new share but does not delete the old key_id
. It is highly recommended to delete the old key_id
after the refresh operation is successful.
The motivation for using refresh is to enhance security by switching the secret key material frequently, this means that an adversary will need to compromise multiple devices at the same time in order to compromise the private key.
Request
Header Parameters
The AUTHORIZATION
header must be set to the API Key of the user. The API Key is returned when a new user is created using the /admin/create-user
endpoint.
- application/json
Body
required
Responses
- 200
- 400
- 401
- 404
- 500
- application/json
- Schema
- Example (from schema)
Schema
{
"key_id": "string"
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [already_performed_keygen
, bad_n_and_t_params
, bad_request_params
, batch_too_large
, executor_result
, key_id_not_exists
, key_operation_before_keygen
, policy_in_use_by_keys
, policy_in_use_by_users
, policy_not_found
, policy_validation_failed
, room_creation_problem
, rule_in_use
, rule_not_found
, rule_not_in_policy
, unique_violation
, user_id_not_exists
, you_have_to_be_admin
]
{
"err_msg": "string",
"err_type": "already_performed_keygen"
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [access_denied
]
{
"err_msg": "string",
"err_type": "access_denied"
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [not_found
]
{
"err_msg": "string",
"err_type": "not_found"
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [internal_problem
]
{
"err_msg": "string",
"err_type": "internal_problem"
}