From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
<c.heiss@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 2/2] ui: ldap: add 'Check connection' checkbox as advanced option
Date: Fri, 28 Jul 2023 10:37:12 +0200 [thread overview]
Message-ID: <CUDO35NLCIJ3.3FAGR2E8RPDU6@pali> (raw)
In-Reply-To: <20230727133341.1009881-3-c.heiss@proxmox.com>
On Thu Jul 27, 2023 at 3:33 PM CEST, Christoph Heiss wrote:
> 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.
As mentioned in my other reply, I think setting the new parameter by default
should not be a problem, as long as it is only in the GUI.
>
> --- 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) {
AD realms have their own GUI component, so I guess it would also make sense to
add the new parameter there.
next prev parent reply other threads:[~2023-07-28 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 13:33 [pve-devel] [PATCH access-control/manager 0/2] ldap: check bind connection on realm add/update Christoph Heiss
2023-07-27 13:33 ` [pve-devel] [PATCH access-control 1/2] api: domains: add off-by-default `check-connection` parameter Christoph Heiss
2023-07-28 8:29 ` Lukas Wagner
2023-08-01 9:17 ` Christoph Heiss
2023-07-27 13:33 ` [pve-devel] [PATCH manager 2/2] ui: ldap: add 'Check connection' checkbox as advanced option Christoph Heiss
2023-07-28 8:37 ` Lukas Wagner [this message]
2023-08-01 9:18 ` Christoph Heiss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CUDO35NLCIJ3.3FAGR2E8RPDU6@pali \
--to=l.wagner@proxmox.com \
--cc=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox