mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Improving the login system and adding a new page to add new users. #1122
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#1122
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 @shawn3308 on GitHub (May 26, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
Other
🔖 Feature description
I was thinking that you could directly ask for a username and password whenever we run the installation script so that whenever we reach out to the site it doesn't ask the new user to create my account there and add a page where we can add new users.
✔️ Solution
So whenever we are done setting up this monitor and go to the site you already have an username and a password to log in with so it will not ask you to create a account over there and if you want to invite one of your friends to the panel there should be a page where you can add your friends email ID and password so that they can login into the monitor.
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Dec 3, 2023):
@shawn3308
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #128 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ I am going to close this as a duplicate.