[GH-ISSUE #176] notify users on auth errors #164

New issue

Closed

opened 2026-02-26 09:36:13 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 09:36:13 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Nov 7, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/176

Originally assigned to: @ThomasWaldmann on GitHub.

if an update request has no or wrong credentials, this does not increment the client faults counter.
this is because we do not know who sent the update request (without auth, this could be anybody, not only the owner of that host).

but we can assume that in most cases it really IS the owner of the host who fails to send correct auth and just does not notice that the updates are not working.

Some updaters will retry and retry and retry rather often, without a chance to success (this is NOT compliant to the dyndns2 specs btw, updaters need to STOP on errors).

What we could do is to introduce a separate counter for auth errors and send a notification to the record owner in case the auth errors are over some threshold.

Also, on the web host view, it could show the auth errors.

Originally created by @ThomasWaldmann on GitHub (Nov 7, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/176 Originally assigned to: @ThomasWaldmann on GitHub. if an update request has no or wrong credentials, this does not increment the client faults counter. this is because we do not know who sent the update request (without auth, this could be anybody, not only the owner of that host). but we can assume that in most cases it really IS the owner of the host who fails to send correct auth and just does not notice that the updates are not working. Some updaters will retry and retry and retry rather often, without a chance to success (this is NOT compliant to the dyndns2 specs btw, updaters need to STOP on errors). What we could do is to introduce a separate counter for auth errors and send a notification to the record owner in case the auth errors are over some threshold. Also, on the web host view, it could show the auth errors.

kerem

2026-02-26 09:36:13 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 09:36:14 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Nov 15, 2014):

note: email notification is not implemented yet, but maybe problematic anyway:

if we have auth errors and send emails too early, the user is maybe still in the process of configuring his updater, so it is too early. also, we should not notify by email for each auth error (it could be someone else, not the legitimate user). if we wait too long, the person configuring the updater is maybe not at the right place any more...

So, better just display it on the web UI, the user should see it there while configuring his updater and also later when he looks there in case of problems.

@ThomasWaldmann commented on GitHub (Nov 15, 2014): note: email notification is not implemented yet, but maybe problematic anyway: if we have auth errors and send emails too early, the user is maybe still in the process of configuring his updater, so it is too early. also, we should not notify by email for each auth error (it could be someone else, not the legitimate user). if we wait too long, the person configuring the updater is maybe not at the right place any more... So, better just display it on the web UI, the user should see it there while configuring his updater and also later when he looks there in case of problems.