On 10/22/19 3:50 PM, Fabian Grünbichler wrote:
> On October 22, 2019 3:32 pm, Thomas Lamprecht wrote:
>> On 10/22/19 3:22 PM, Fabian Grünbichler wrote:
>>> On October 22, 2019 1:44 pm, Tim Marx wrote:
Do we really want a enable/disable property?
Wouldn't it be enough to delete the token?
On October 22, 2019 3:32 pm, Thomas Lamprecht wrote:
> On 10/22/19 3:22 PM, Fabian Grünbichler wrote:
>> On October 22, 2019 1:44 pm, Tim Marx wrote:
>>> Do we really want a enable/disable property?
>>> Wouldn't it be enough to delete the token?
>>
>> there's a difference though. I might have
On 10/22/19 3:22 PM, Fabian Grünbichler wrote:
> On October 22, 2019 1:44 pm, Tim Marx wrote:
>> Do we really want a enable/disable property?
>> Wouldn't it be enough to delete the token?
>
> there's a difference though. I might have configured the token on X
> systems, but want to temporarily
On October 22, 2019 1:44 pm, Tim Marx wrote:
> Do we really want a enable/disable property?
> Wouldn't it be enough to delete the token?
there's a difference though. I might have configured the token on X
systems, but want to temporarily disable it. since the actual token
value is generated on
Do we really want a enable/disable property?
Wouldn't it be enough to delete the token?
> Fabian Grünbichler hat am 17. Oktober 2019 15:14
> geschrieben:
>
>
> and integration for user API endpoints.
>
> Signed-off-by: Fabian Grünbichler
> ---
>
> Notes:
> pveum integration will come
and integration for user API endpoints.
Signed-off-by: Fabian Grünbichler
---
Notes:
pveum integration will come in a future version, but
pveum token add/modify/delete [OPTIONS]
or
pveum user token add/modify/delete [OPTIONS]
seem like likely
