On 19.8.2015 14:39, Christian Heimes wrote:
On 2015-08-19 14:12, Jan Cholasta wrote:
The new flags should be handled in vault_find's pre_callback instead of
vault's get_dn, as they are exclusive to vault_find and worse yet,
conflict with vault_{add,remove}_{owner,member}'s flags, leading to
unwa
On 2015-08-19 14:12, Jan Cholasta wrote:
> The new flags should be handled in vault_find's pre_callback instead of
> vault's get_dn, as they are exclusive to vault_find and worse yet,
> conflict with vault_{add,remove}_{owner,member}'s flags, leading to
> unwanted behavior:
>
> $ ipa vault-add-mem
On 08/19/2015 02:12 PM, Jan Cholasta wrote:
Hi,
On 19.8.2015 13:39, Christian Heimes wrote:
The vault-find plugin has two additional arguments to list all
service vaults or user vaults. Since the name of a vault is only unique
for a particular user or service, the commands also print the vault
Hi,
On 19.8.2015 13:39, Christian Heimes wrote:
The vault-find plugin has two additional arguments to list all
service vaults or user vaults. Since the name of a vault is only unique
for a particular user or service, the commands also print the vault user
or vault service. The virtual attributes
The vault-find plugin has two additional arguments to list all
service vaults or user vaults. Since the name of a vault is only unique
for a particular user or service, the commands also print the vault user
or vault service. The virtual attributes were added in rev
01dd951ddc0181b559eb3dd5ff0336c8
