From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox Backup Server development discussion"
<pbs-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] api tokens: add authorization method
Date: Fri, 30 Oct 2020 13:36:29 +0100 [thread overview]
Message-ID: <65564cb2-c39c-e850-2103-8213388f1dde@proxmox.com> (raw)
In-Reply-To: <20201030121038.2699389-1-f.gruenbichler@proxmox.com>
On 30.10.20 13:10, Fabian Grünbichler wrote:
> and properly decode secret (which is a no-op with the current scheme).
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
> note: this breaks older clients obviously, but given the short time it's
> been out, and the lack of documentation I think this is okay..
>
and we're still in beta :-)
> src/client/http_client.rs | 4 ++--
> src/server/rest.rs | 9 ++++++++-
> 2 files changed, 10 insertions(+), 3 deletions(-)
>
>
applied, thanks! Made a followupto also accept the `PBSAPIToken=<...>` variant to
be consistent with PVE, like discussed.
prev parent reply other threads:[~2020-10-30 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 12:10 [pbs-devel] " Fabian Grünbichler
2020-10-30 12:36 ` Thomas Lamprecht [this message]
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=65564cb2-c39c-e850-2103-8213388f1dde@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pbs-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