auth ui: fix value not defined in enumeration
error
...when editing LDAP realm sync settings and only a single property is empty and thus to be deleted (e.g. values.delete = "filter"). If `delete` is a simple string and not an array, `Proxmox.Utils.delete_if_default` simply creates a comma-separated list, (e.g. value.delete = "filter,sync-attributes"). When the properties from the other panel are evaluated and added to the the `delete` property, comma-separated list format is not considered, leading to a final value for `delete` that could look like this: value.delete = { "server2", "comment", "filter,sync-attributes" } This commit fixes this by splitting `delete` in case it is a string. Reported-by: Friedrich Weber <f.weber@proxmox.com> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
This commit is contained in:
parent
78970361b3
commit
bfb750a564
@ -243,6 +243,11 @@ Ext.define('Proxmox.panel.LDAPSyncInputPanel', {
|
||||
Proxmox.Utils.delete_if_default(values, 'sync-defaults-options');
|
||||
Proxmox.Utils.delete_if_default(values, 'sync-attributes');
|
||||
|
||||
// Force values.delete to be an array
|
||||
if (typeof values.delete === 'string') {
|
||||
values.delete = values.delete.split(',');
|
||||
}
|
||||
|
||||
if (me.isCreate) {
|
||||
delete values.delete; // on create we cannot delete values
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user