[GH-ISSUE #1596] OIDC for User Auth #1121

Open
opened 2026-05-07 00:30:24 +02:00 by BreizhHardware · 4 comments

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

Originally created by @nsauter on GitHub (Feb 7, 2026). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1596 :bulb: **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. :computer: ntfy server
Author
Owner

@Gunni commented on GitHub (Apr 26, 2026):

I'd like to use my self hosted Pocket-ID.

<!-- gh-comment-id:4322250780 --> @Gunni commented on GitHub (Apr 26, 2026): I'd like to use my self hosted Pocket-ID.
Author
Owner

@litmaj0r commented on GitHub (Apr 27, 2026):

Leveraging existing KeyCloak infra for users and auth would be great (just a simple role addition)

<!-- gh-comment-id:4323487955 --> @litmaj0r commented on GitHub (Apr 27, 2026): Leveraging existing KeyCloak infra for users and auth would be great (just a simple role addition)
Author
Owner

@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.

<!-- gh-comment-id:4370641820 --> @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.
Author
Owner

@wakearray commented on GitHub (May 6, 2026):

+1 for generic OIDC support. Even better would be groups/roles/claims support for controlling notification access. I'd love to have this working with my Kanidm instance.

<!-- gh-comment-id:4390893071 --> @wakearray commented on GitHub (May 6, 2026): +1 for generic OIDC support. Even better would be groups/roles/claims support for controlling notification access. I'd love to have this working with my Kanidm instance.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#1121
No description provided.