[GH-ISSUE #1208] [feature request] Client certificate support for TLS authentication #855

New issue

Closed

opened 2026-05-07 00:28:12 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-07 00:28:12 +02:00

Owner

Originally created by @lescisin on GitHub (Oct 30, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1208

Hi there - Thanks for all of the excellent work on this project. Really great stuff - I've only been using it for about a week and already it's been helpful for me. I especially appreciate the simplicity of posting messages - it makes it so easy to integrate into other services.

My suggestion:

I was hoping to use client certificates on my front end proxy for TLS authentication to ntfy. I configured my proxy for this and I'm able to authenticate and then access ntfy via browser - I get prompted for the client cert and all works. (hooray!) However, doing the same on the android app, I get the error below.

I'm thinking that the client Android app does not support client certificates based on this. I am submitting this suggestion in hopes that the feature might be considered as a future enhancement.

Originally created by @lescisin on GitHub (Oct 30, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1208 Hi there - Thanks for all of the excellent work on this project. Really great stuff - I've only been using it for about a week and already it's been helpful for me. I especially appreciate the simplicity of posting messages - it makes it so easy to integrate into other services. My suggestion: I was hoping to use client certificates on my front end proxy for TLS authentication to ntfy. I configured my proxy for this and I'm able to authenticate and then access ntfy via browser - I get prompted for the client cert and all works. (hooray!) However, doing the same on the android app, I get the error below. I'm thinking that the client Android app does not support client certificates based on this. I am submitting this suggestion in hopes that the feature might be considered as a future enhancement. ![Screenshot 2024-10-29 8 50 35 PM](https://github.com/user-attachments/assets/065e5d3f-af9a-4cdf-bf7f-cba80c61c891)

BreizhHardware

2026-05-07 00:28:12 +02:00

closed this issue
added the
enhancement
label

BreizhHardware commented

2026-05-07 00:28:13 +02:00

Author

Owner

@kk7ds commented on GitHub (Dec 26, 2024):

I would really like this as well! I use user cert auth for everything (related to my automation systems) and it's definitely be preferable to be able to do that for ntfy as well instead of having to have a separate scheme.

@kk7ds commented on GitHub (Dec 26, 2024): I would really like this as well! I use user cert auth for everything (related to my automation systems) and it's definitely be preferable to be able to do that for ntfy as well instead of having to have a separate scheme.

BreizhHardware commented

2026-05-07 00:28:13 +02:00

Author

Owner

@hackerd2501 commented on GitHub (Aug 2, 2025):

I would like that as well. Same problem as kk7ds.
I have my homeassistant connected with a cloudflare tunnel where access is secured with a cloudflare generated client certificate. Homeassistant companion asks me for the client certificate at session start.

For server errors I use ntfy. But that works only at home.

I can connect to my local server over the internet by using chrome, which asks me for the client certificate.

The ntfy app cannot connect, it asks me for username and password instead.

@hackerd2501 commented on GitHub (Aug 2, 2025): I would like that as well. Same problem as kk7ds. I have my homeassistant connected with a cloudflare tunnel where access is secured with a cloudflare generated client certificate. Homeassistant companion asks me for the client certificate at session start. For server errors I use ntfy. But that works only at home. I can connect to my local server over the internet by using chrome, which asks me for the client certificate. The ntfy app cannot connect, it asks me for username and password instead.

BreizhHardware commented

2026-05-07 00:28:13 +02:00

Author

Owner

@binwiederhier commented on GitHub (Jan 18, 2026):

Duplicate. This was implemented and will be released in 1.22.x (next Android release), see #215, #530, etc.

@binwiederhier commented on GitHub (Jan 18, 2026): Duplicate. This was implemented and will be released in 1.22.x (next Android release), see #215, #530, etc.