Update the software FIPS mode or enable conversion of non-encrypted metadata volumes non-NAE aggregates
PATCH /security
Introduced In: 9.8
Updates the software FIPS mode or enables conversion of non-encrypted metadata volumes to encrypted metadata volumes and non-NAE aggregates to NAE aggregates.
Parameters
Name | Type | In | Required | Description |
---|---|---|---|---|
return_records |
boolean |
query |
False |
The default is false. If set to true, the records are returned.
|
return_timeout |
integer |
query |
False |
The number of seconds to allow the call to execute before returning. When doing a POST, PATCH, or DELETE operation on a single record, the default is 0 seconds. This means that if an asynchronous operation is started, the server immediately returns HTTP code 202 (Accepted) along with a link to the job. If a non-zero value is specified for POST, PATCH, or DELETE operations, ONTAP waits that length of time to see if the job completes so it can return something other than 202.
|
Request Body
Name | Type | Description |
---|---|---|
_links |
||
fips |
Cluster-wide Federal Information Processing Standards (FIPS) mode information. |
|
onboard_key_manager_configurable_status |
Indicates whether the Onboard Key Manager can be configured in the cluster. |
|
software_data_encryption |
Cluster-wide software data encryption related information. |
Example request
{
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"onboard_key_manager_configurable_status": {
"code": "65537300",
"message": "No platform support for volume encryption in following nodes - node1, node2."
}
}
Response
Status: 202, Accepted
Name | Type | Description |
---|---|---|
job |
Example response
{
"job": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"uuid": "string"
}
}
Error
Status: Default
ONTAP Error Response Codes
Error Code | Description |
---|---|
52428830 |
Cannot enable FIPS-compliant mode because the configured minimum security strength for certificates is not compatible. |
52559974 |
Cannot enable FIPS-compliant mode because a certificate that is not FIPS-compliant is in use. |
196608081 |
Cannot start software encryption conversion while there are data volumes in the cluster. |
196608082 |
The operation is not valid when the MetroCluster is in switchover mode. |
Name | Type | Description |
---|---|---|
error |
Example error
{
"error": {
"arguments": [
{
"code": "string",
"message": "string"
}
],
"code": "4",
"message": "entry doesn't exist",
"target": "uuid"
}
}
Definitions
See Definitions
href
Name | Type | Description |
---|---|---|
href |
string |
_links
Name | Type | Description |
---|---|---|
self |
fips
Cluster-wide Federal Information Processing Standards (FIPS) mode information.
Name | Type | Description |
---|---|---|
enabled |
boolean |
Indicates whether or not the software FIPS mode is enabled on the cluster. Our FIPS compliance involves configuring the use of only approved algorithms in applicable contexts (for example TLS), as well as the use of formally validated cryptographic module software implementations, where applicable. The US government documents concerning FIPS 140-2 outline the relevant security policies in detail. |
onboard_key_manager_configurable_status
Indicates whether the Onboard Key Manager can be configured in the cluster.
Name | Type | Description |
---|---|---|
code |
integer |
Code corresponding to the status message. Returns a 0 if the Onboard Key Manager can be configured in the cluster. |
message |
string |
Reason that Onboard Key Manager cannot be configured in the cluster. |
supported |
boolean |
Set to true if the Onboard Key Manager can be configured in the cluster. |
software_data_encryption
Cluster-wide software data encryption related information.
Name | Type | Description |
---|---|---|
conversion_enabled |
boolean |
Indicates whether or not software encryption conversion is enabled on the cluster. A PATCH request initiates the conversion of all non-encrypted metadata volumes in the cluster to encrypted metadata volumes and all non-NAE aggregates to NAE aggregates. For the PATCH request to start, the cluster must have either an Onboard or an external key manager set up and the aggregates should either be empty or have only metadata volumes. No data volumes should be present in any of the aggregates in the cluster. For MetroCluster configurations, a PATCH request enables conversion on all the aggregates and metadata volumes of both local and remote clusters and is not allowed when the MetroCluster is in switchover state. |
security_config
Name | Type | Description |
---|---|---|
_links |
||
fips |
Cluster-wide Federal Information Processing Standards (FIPS) mode information. |
|
onboard_key_manager_configurable_status |
Indicates whether the Onboard Key Manager can be configured in the cluster. |
|
software_data_encryption |
Cluster-wide software data encryption related information. |
job_link
Name | Type | Description |
---|---|---|
_links |
||
uuid |
string |
The UUID of the asynchronous job that is triggered by a POST, PATCH, or DELETE operation. |
error_arguments
Name | Type | Description |
---|---|---|
code |
string |
Argument code |
message |
string |
Message argument |
error
Name | Type | Description |
---|---|---|
arguments |
array[error_arguments] |
Message arguments |
code |
string |
Error code |
message |
string |
Error message |
target |
string |
The target parameter that caused the error. |