Troubleshooting
Problem
How to update ISAM configuration file parameters if they are multi-value within a single stanza when using the ISAM Web Services REST API?
Symptom
Some parameters in ISAM configuration files may exist numerous times within a specific stanza in order to support multiple values, for example in a WebSEAL configuration file the following may exist:
[ssl-qop-mgmt-default]
default = AES-128
default = RC2-128
default = RC4-128
default = DES-168
The REST API for 'updating a configuration entry or entries by stanza - Reverse Proxy' has the following syntax that only permits the parameter name in the stanza to be expressed:
https://{appliance_hostname}/wga/reverseproxy/{reverseproxy_id}/configuration/stanza/{stanza_id}/entry_name/{entry_name_id}
The consequence is that a specific multi-value parameter cannot be modified using this REST API call as the syntax only identifies the parameter to update and not the value.
Resolving The Problem
Use explicit "delete" and then "add" REST API calls, rather than an "update" API call. For example to update the existing entry, "default = AES-128" to "default = AES-256":
(1) Remove the existing explicit value:
curl -k -v -H "Accept:application/json" --user admin:<password> -X DELETE
https://<hostname>/wga/reverseproxy/<instance>/configuration/stanza/ssl-
qop-mgmt-default/entry_name/default/value/AES-128
(2) Add the new value:
curl -k -v -H "Accept:application/json" --user admin:<password> -d@addParam.json -X POST https://<hostname>/wga/reverseproxy/<instance>/configuration/stanza/ssl-qop-mgmt-default/entry_name
Where the addParam.json file contains:
{
entries: [
["default", "AES-256"],
]
}
Product Synonym
ISAM;REST;API;update;modify;multi-value;parameter;entry_name_id
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21970060