Skip to main content

Update the application configuration

PUT 

/tap/api/v3/config/application

Updates the application configuration. Only these fields are written: customerName, userLimit, userValidateEmailDomain, userValidateEmailDomainWhitelist, sendWelcomeEmail, sendWelcomeEmailWithAttachment, showBundleLinks, enableResourceRoleMasquerade, enableAwsApiLogging, the log fields except logIgnoreResponseCodesSuccess and logAccountOverrides, enableOCSP, certificateKeySize, certificateHashAlgorithm, and the cors fields. Omitted or null fields keep their values, except userValidateEmailDomainWhitelist: when it is empty or null, or omitted while no domains are allowed, the deployment's default allowed domains are written. An omitted field is written again with its current value. Every written field is stored as a Managed Configuration Value, which PUT /tap/api/v3/config/application/item then rejects. userValidateEmailDomainWhitelist, logIgnoreServices, logIgnoreServicesNever, logIgnoreResponseCodes, logRedactFields, corsAccessControlAllowOrigin, and corsAccessControlAllowMethods are split on commas, semicolons, spaces, and newlines, de-duplicated, and stored separated by spaces. Requires the super_admin role.

Request​

Responses​

The submitted configuration, echoed back. An omitted field holds its value from before the update and a field submitted as null is omitted, except that an empty or null userValidateEmailDomainWhitelist holds the default allowed domains that were written. Every other field is returned as submitted: list values are not normalized, and a value submitted for a field that is not written (such as awsAccountId or enableToolFirewallRules) is echoed but not stored.