mirror of
https://github.com/proxmoxer/proxmoxer.git
synced 2026-04-25 07:06:00 +03:00
[PR #25] [MERGED] Deprecate old token auth #139
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#139
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?
📋 Pull Request Information
Original PR: https://github.com/proxmoxer/proxmoxer/pull/25
Author: @jhollowe
Created: 5/20/2020
Status: ✅ Merged
Merged: 5/21/2020
Merged by: @morph027
Base:
develop← Head:deprecate-old-token-auth📝 Commits (3)
24c04faDepricate existing token auth0c4f3b0Refactor names to be distinct95c9268Fix renaming error📊 Changes
2 files changed (+26 additions, -20 deletions)
View changed files
📝
proxmoxer/backends/https.py(+25 -19)📝
tests/https_tests.py(+1 -1)📄 Description
The
ProxmoxHTTPTokenAuthauth is redundant. If the user needs a stateless authentication, the API Token auth can now be used; if the user wants to use the user/password auth, the existing ticket can just be passed as the password and a fresh ticket and CSRF token will be generated.It will also cause unneeded confusion now with the API Token auth which sounds similar but is completely different.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.