mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-15 07:35:49 -06:00
[GH-ISSUE #1596] OIDC for User Auth #1122
Labels
No labels
ai-generated
android-app
android-app
android-app
build
build
dependencies
docs
enhancement
enhancement
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
server
server
unified-push
web-app
website
🔒 security
🔥 HOT
🪲 bug
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/ntfy#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 @nsauter on GitHub (Feb 7, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1596
💡 Idea
I really like how OIDC is getting more and more used even in home setups. Im using it too for most of my services since i support a whole family with access to different services. I really want to move from Telegram Bots for notifications to a dedicated push notification system (because telegram annoys me). But i dont want to have local accounts on my nfty server when every other system uses oidc. I would love to have oicd for auth in nfty.
💻 ntfy server
@Gunni commented on GitHub (Apr 26, 2026):
I'd like to use my self hosted Pocket-ID.
@litmaj0r commented on GitHub (Apr 27, 2026):
Leveraging existing KeyCloak infra for users and auth would be great (just a simple role addition)
@bitmotivator commented on GitHub (May 4, 2026):
I would like to also support this idea, having a single source of users would make a lot easier. I would be happy to contribute the server side implementation.