mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #3964] [Feature Request]: Improve password copy behavior at user creation #1784
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1784
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 @mruiterHU on GitHub (Apr 15, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3964
Originally assigned to: @kris6673 on GitHub.
Please confirm:
Problem Statement
Currently, when creating a new user in CIPP, the password is either auto-generated or manually entered by the engineer. After clicking "Submit", the password is shown below with a copy button.
However, using the copy button also includes the label text (e.g., Password:), which makes it inconvenient to paste the password directly into other tools or environments.
Suggestion:
This would improve usability and reduce small copy/paste frustrations during user onboarding.
Benefits for MSPs
This would be a small quality-of-life update that makes copying and pasting newly created passwords quicker, cleaner, and less error-prone.
sponsering via: https://github.com/hypecipp
Value or Importance
More of a Quality of Life feature
PowerShell Commands (Optional)
No response
@kris6673 commented on GitHub (Apr 15, 2025):
I would like to work on this please!
@github-actions[bot] commented on GitHub (Apr 15, 2025):
Great! I assigned you (@kris6673) to the issue. Have fun working on it!