Rename or split cli --qr option #219
Labels
No labels
Compat/Breaking
Component/Enclave-Builder
Component/Infrastructure
Deploy/BYOC
Deploy/Full-managed
Deploy/Self-hosted
Interface/API
Interface/CLI
Interface/Git
Interface/Web
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
public/platform#219
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?
The cli
--qroption has two paths for a user to login successfully; via QR code and via a provided link (WebAuthn).The option should be renamed to reflect this multiple use, or the functionality should be split into two options if that is easy enough.
Related: issue #217 and PR #218
Consolidated scope from #217
Track the missing browser/WebAuthn help documentation from #217 here alongside the QR-option naming/splitting decision. This requirement remains unfinished, not fixed by consolidation.
caution --helpandcaution login --helpclearly describe the browser-link/WebAuthn authentication option as well as QR use, including the distinction from local security-key authentication.Might not be bad to offer both a link and a qr code in all cases. That would simplify things overall.
Consolidated #217 into this issue. Its missing CLI help requirement is now explicitly retained in the acceptance checklist above. This is unfinished work, not a fixed bug; PR #218 was closed without merging. Existing QR/browser-link naming and behavior scope is unchanged.