The checkbox is enabled by default for new realms, setting the new
`check-connection` parameter.
Won't effect existing configurations, i.e. being opt-in for them, to not
break existing setups.
Signed-off-by: Christoph Heiss <c.he...@proxmox.com>
---
As this uses the newly introduced `check-connection` API parameter, a
bump of libpve-access-control will be needed.
www/manager6/dc/AuthEditLDAP.js | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/www/manager6/dc/AuthEditLDAP.js b/www/manager6/dc/AuthEditLDAP.js
index 2ce16e58c..6f0472ae3 100644
--- a/www/manager6/dc/AuthEditLDAP.js
+++ b/www/manager6/dc/AuthEditLDAP.js
@@ -79,6 +79,21 @@ Ext.define('PVE.panel.LDAPInputPanel', {
},
];
+ me.advancedItems = [
+ {
+ xtype: 'proxmoxcheckbox',
+ fieldLabel: gettext('Check connection'),
+ name: 'check-connection',
+ uncheckedValue: 0,
+ checked: me.isCreate,
+ autoEl: {
+ tag: 'div',
+ 'data-qtip':
+ gettext('Verify connection parameters and bind
credentials on save'),
+ },
+ },
+ ];
+
me.callParent();
},
onGetValues: function(values) {
--
2.41.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
