mirror of
https://github.com/proxmoxer/proxmoxer.git
synced 2026-04-25 23:26:00 +03:00
[GH-ISSUE #31] OTP support for https backend #13
Labels
No labels
backend:https
backend:local
backend:openssh
backend:ssh_paramiko
pull-request
status:ansible-issue
status:help-wanted
status:info-needed
status:proxmox-issue
status:review-needed
type:bug 🐞
type:dependency ⛓️
type:docs 📝
type:enhancement ⏫
type:maintenance 🛠️
type:meta
type:question ❓
type:request ✋
type:testing 🧪
version:1.x
version:latest
version:py2
version:py3
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxmoxer#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @antonakv on GitHub (Jul 3, 2020).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/31
Ticket request is failing with proxmoxer.core.ResourceException: 401 Unauthorized: No ticket - b'' when otp is enabled but not set in REST api request.
Please add otp token support for https backend
otp field is optional here https://pve.proxmox.com/pve-docs/api-viewer/index.html#/access/ticket
@jhollowe commented on GitHub (Jul 3, 2020):
We can definitely add this, but I would suggest using API tokens as they can be locked down more and can be disabled easily if they are compromised.
@jhollowe commented on GitHub (Jul 3, 2020):
note-to-self: I imagine PVE will renew valid tickets without OTP, but we should check that before attempting to add support for OTP.
@antonakv commented on GitHub (Jul 4, 2020):
@jhollowe That's possible, though valid ticket generation is not possible when OTP is enabled for all the accounts.
@antonakv commented on GitHub (Jul 4, 2020):
API tokens aren't available in my configuration. I tried to do before.