starred/ntfy

Fork 0

mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 08:26:00 +02:00

[GH-ISSUE #382] Android: UnifiedPush subscription not using saved user credentials #294

New issue

Closed

opened 2026-05-07 00:22:41 +02:00 by BreizhHardware · 6 comments

BreizhHardware commented

2026-05-07 00:22:41 +02:00

Owner

Originally created by @ryester19 on GitHub (Aug 17, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/382

Using Ntfy server 1.27.2, Android Ntfy app 1.13.0, and Android Element 1.4.32
ACL is enabled on the server, and auth-default-access set to 'deny-all'

The subscription that Element sets up for UnifiedPush use does not use the saved user credentials in the ntfy app. The user is an admin, and the "Managed users" page does say the user is being used for this topic. The only error I see in the server log is a "unauthorized: unauthorized" message

In order to get Element to pass the "Test Push" test, I have to give anonymous read-write access to the topic that's created by Element

Android log:
https://nopaste.net/PFREHjyS0Q

Originally created by @ryester19 on GitHub (Aug 17, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/382 Using Ntfy server 1.27.2, Android Ntfy app 1.13.0, and Android Element 1.4.32 ACL is enabled on the server, and auth-default-access set to 'deny-all' The subscription that Element sets up for UnifiedPush use does not use the saved user credentials in the ntfy app. The user is an admin, and the "Managed users" page does say the user is being used for this topic. The only error I see in the server log is a "unauthorized: unauthorized" message In order to get Element to pass the "Test Push" test, I have to give anonymous read-write access to the topic that's created by Element Android log: https://nopaste.net/PFREHjyS0Q

BreizhHardware

2026-05-07 00:22:41 +02:00

closed this issue
added the
android-app

question
labels

BreizhHardware commented

2026-05-07 00:22:42 +02:00

Author

Owner

@MaximilianGaedig commented on GitHub (Aug 18, 2022):

Just ran into the same issue, the workaround for now is using the ntfy.sh server for unified push and your own for other things but that's no real workaround as you are not using your server

@MaximilianGaedig commented on GitHub (Aug 18, 2022): Just ran into the same issue, the workaround for now is using the ntfy.sh server for unified push and your own for other things but that's no real workaround as you are not using your server

BreizhHardware commented

2026-05-07 00:22:42 +02:00

Author

Owner

@binwiederhier commented on GitHub (Aug 18, 2022):

This is not a bug in ntfy, but rather a design limitation of UnifiedPush (UP). In UP, the URL is the secret, user/password cannot be used in the spec.

This explains this in more detail: https://unifiedpush.org/users/distributors/ntfy/#limit-access-to-some-users

Specifically this section:

Pushers still need to be able to write to UnifiedPush topics to send push notifications. Add a rule to make UnifiedPush topics (they all start with “up”) world-writeable: ntfy access '*' 'up*' write-only

@binwiederhier commented on GitHub (Aug 18, 2022): This is not a bug in ntfy, but rather a design limitation of UnifiedPush (UP). In UP, the URL is the secret, user/password cannot be used in the spec. This explains this in more detail: https://unifiedpush.org/users/distributors/ntfy/#limit-access-to-some-users Specifically this section: > Pushers still need to be able to write to UnifiedPush topics to send push notifications. Add a rule to make UnifiedPush topics (they all start with “up”) world-writeable: `ntfy access '*' 'up*' write-only`

BreizhHardware commented

2026-05-07 00:22:42 +02:00

Author

Owner

@binwiederhier commented on GitHub (Aug 18, 2022):

For more questions about UP, please check out the UP Matrix room(s)

@binwiederhier commented on GitHub (Aug 18, 2022): For more questions about UP, please check out the UP Matrix room(s)

BreizhHardware commented

2026-05-07 00:22:43 +02:00

Author

Owner

@ryester19 commented on GitHub (Aug 18, 2022):

Gotcha. To get around this limitation in a more user-friendly way, could we add a ACL sub-option in the config file or an alias toggle in the 'ntfy access' command?

@ryester19 commented on GitHub (Aug 18, 2022): Gotcha. To get around this limitation in a more user-friendly way, could we add a ACL sub-option in the config file or an alias toggle in the 'ntfy access' command?

BreizhHardware commented

2026-05-07 00:22:43 +02:00

Author

Owner

@binwiederhier commented on GitHub (Aug 29, 2022):

@ryester19 Any suggestions?

@binwiederhier commented on GitHub (Aug 29, 2022): @ryester19 Any suggestions?

BreizhHardware commented

2026-05-07 00:22:43 +02:00

Author

Owner

@binwiederhier commented on GitHub (Sep 3, 2022):

Let me know if you have any suggestions. For now I'll close this issue.

@binwiederhier commented on GitHub (Sep 3, 2022): Let me know if you have any suggestions. For now I'll close this issue.