204 |
|
Security settings record successfully accepted. |
400 |
text/plain
|
Bad request. |
400 |
application/vnd.plcm.plcm-error+xml
|
Conflicting security settings. When "Allow non-FIPS ciphers" is false then
"Skip validation of certificates received while making outbound connections" must not be true.
|
401 |
application/vnd.plcm.plcm-error+xml
|
User is not authorized to update the security settings |
406 |
application/vnd.plcm.plcm-error+xml
|
Not Acceptable |
409 |
application/vnd.plcm.plcm-error+xml
|
The specified security-mode is not valid in this context.
|
409 |
application/vnd.plcm.plcm-error+xml
|
The specified security options are not valid for the ENHANCED security-mode.
When specifying an ENHANCED security mode, the following settings should either be false or not specified:
allow-a-non-events (v1,v2)
allow-anon-events (v3+)
allow-booting-from-usb-or-optical-drive
allow-console-access (v3+)
allow-linux-console-access (v1,v2)
allow-non-tls-for-ldap (v3+)
allow-ssh-access (v3+)
allow-ssh-root-access (v3+)
basic-calendar-auth-allowed
http-calendar-notifications-allowed
non-fips-cipher-allowed (v2)
skip-call-signaling-cert
skip-server-cert-validation (v1,v2)
unencrypted-enterprise-directory-access-allowed
unencrypted-mcu-access-allowed
|
409 |
application/vnd.plcm.plcm-error+xml
|
The request contained ETags in both the header (header-ETag) and the
body (body-ETag) and they do not match.
|
412 |
application/vnd.plcm.plcm-error+xml
|
The resource has changed on the server. The API client must retrieve
the latest resource version, apply the resource modifications,
then update to the server.
|
428 |
application/vnd.plcm.plcm-error+xml
|
The API client must supply the ETag in the message body that is
bounded by
the "entity-tag" XML tag. Refer to the
"plcm-security-settings.xsd" for details.
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.
|
428 |
|
Security settings information has changed since the last retrieval.
Note: The response will contain the ETag value and link that reflects
the server's security settings resource in the HTTP response
header.
The API client must supply the ETag in the message body that is
bounded by
the "entity-tag" XML tag. Refer to the "plcm-security-settings.xsd"
for details.
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.
The "plcm-security-settings" ETag can be accessed from the initial
retrieval result's HTTP
response header.This also assumes no other client made changes to
Security settings records on the server.
|