mirror of
https://github.com/proxmoxer/proxmoxer.git
synced 2026-04-25 07:06:00 +03:00
[GH-ISSUE #156] Weird OTP problem #82
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#82
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 @addelovein on GitHub (Jan 24, 2024).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/156
Originally assigned to: @jhollowe on GitHub.
Most likely im doing something wrong...
Returns
proxmoxer.core.AuthenticationError: Couldn't authenticate user: user@pve to https://MYHOST:443/api2/json/access/ticket
If i remove OTP and try a user without TFA... It logs in.
The user that fails can log in directly to proxmox using OTP
The failing user works if i remove TFA from proxmox and OTP here...
Am i missing someting? Going a bit crazy here....
@addelovein commented on GitHub (Jan 24, 2024):
@jhollowe commented on GitHub (Jan 24, 2024):
Please try having the OTP be a
strongstring rather than an integer. I don't know if that is the issue, but I think it might be@addelovein commented on GitHub (Jan 24, 2024):
Same issue if I declare totp with totp="292695"
@jhollowe commented on GitHub (Jan 27, 2024):
Can you look at the network traffic in your browser and see what data the
api2/json/access/ticketrequest has?@addelovein commented on GitHub (Jan 27, 2024):
You mean when I log in to proxmox via browser?
First ticket:
Request
Response
Second Ticket (The Real Authentication)
Request
Response
Authenticated.....
That should be enough data ;-)
@jhollowe commented on GitHub (Jan 31, 2024):
I'm not sure. You might try asking in the proxmox forums how to pass OTP values to the
api2/json/access/ticketAPI endpoint. proxmoxer does not do the two-step OTP process and instead just passes the username, password, and OTP all in one request. This may be no longer supported by the Proxmox auth layer and we may need to adjust the login flow if an OTP value is provided.@addelovein commented on GitHub (Jan 31, 2024):
It sure is supported, this code works... Just wrote it based of how proxmox itself authenticates its webui...
@addelovein commented on GitHub (Feb 17, 2024):
No response on this at all?
@jpattWPC commented on GitHub (Feb 18, 2024):
I added #158 to address this on the HTTPS backend. Please let me know if this can be merged into a release.
@jhollowe commented on GitHub (Feb 22, 2024):
@addelovein sorry for the slow response, this fell off my radar.
Thanks @jpattWPC for the PR!
I've started a thread in the PVE forums to see if the single request flow is still supported or if this needs to move to the two-step flow:
https://forum.proxmox.com/threads/single-post-auth-with-otp-no-longer-supported.141830/
@addelovein commented on GitHub (Mar 24, 2024):
I posted a working example...
@jpattWPC commented on GitHub (Mar 24, 2024):
I'm waiting on PR acceptance from the proxmoxer repo, you're correct that 2
step auth is now required. I submitted a PR to fix this issue in the
proxmoxer repo.
On Sun, Mar 24, 2024, 6:55 PM Adde Lovein @.***> wrote: