Avoids that the user selector always pops up and tokenid is normally
more likely to change as the userid gets pre-selected to the one from
the logged in user.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
As else some people could be confused and put in their name, as below
is the email field, and name+email are quite often pairs.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
by increasing the space for the link, and using a boxLabel instead
of fieldLabel, which has better spacing for longer text
also move the e-mail before the directory to have all textboxes together
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
When using a diffstore, we have to specify all fields that are
displayed, otherwise the store does not know which fields to check for
change
for the acme plugin view, 'api' was missing
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we cannot pass 'delete' on create api call, and we have to make
sure that 'default_opts' and 'sync_attributes' are alwyas available,
since they are used in onGetValues
(they were only created during setValues, which is not called
when adding a new realm)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this is not a synchronous api call, so open a taskprogress window
and reload after the task is done
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
if we use a diff/update store combo, we have to load the updatestore
not the diff store, else we get spurious empty grids
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
if the 'default' account exists, make the name field required and
remove the emptytext
get the information by querying the grid store. this may be not
up-to-date, but it is less intrusive that an extra api call that
blocks the window
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we need to parse the config even if it does not exist - it will return
the 'standalone' entry that's needed to be backwards compatible with
existing setups.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
to order a ceritificate, we need at least one configured domain, and
the configured account (or default) must exist
so track the domaincount in the viewmodel and introduce a
'canOrder' formula which is only true when domaincount > 0 and
account is set (if the configured account does not exist, or no account
exists at all we set 'account' to 'null')
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
instead of using API2Request manually, just reload the store of
the accountselector and check if the configured account is in it
this should fix the spurious loading mask of the panel when
loading the accounts
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>