mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
SSO Provider Support for Uptime Kuma Login #3943
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#3943
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 @mxlb-dev on GitHub (Jan 31, 2025).
📑 I have found these related issues/pull requests
none
🏷️ Feature Request Type
Settings
🔖 Feature description
Enable users to leverage their identity / SSO provider (e.g. authentik, authelia, others..) to log into Uptime Kuma.
✔️ Solution
MVP: provide HTTP basic auth as alternative to current HTML login form (SSO provider then acts as proxy to pass-through credentials)
Nice to have: UI toggle between login options
Later release: support for OAuth2/OpenID or similar
❓ Alternatives
No response
📝 Additional Context
No response
@femabeh commented on GitHub (Feb 2, 2025):
I think Something Like openid connect could be useful. And because its and Open Format you could use very identity Provider who Supports it.
@Pyrrha commented on GitHub (Feb 4, 2025):
Related to #553 🙂
This feature would be really nice. An alternative is to configure oauth-proxy as suggested in the linked issue.
@CommanderStorm commented on GitHub (Mar 14, 2025):
Lets track this in said issue instead: