Disabling emails causes 500 error when adding new project members about healthchecks HOT 3 CLOSED

Healthchecks is written with the assumption that working SMTP credentials will be available.

Can you share details about your planned use-case?

• Are you setting up an instance for a homelab or for a company?
• What's the deciding factor why you don't want to use email?
• Email is used to deliver login links. How do you plan to log users in, using external authentication and REMOTE_USER_HEADER?
• Email is used to deliver monthly and weekly reports, and daily or hourly reminders when any checks are down. Are you not planning to use those?
• Email is used to deliver verification code before sensitive actions, would you expect the verification step to be skipped if there is no outgoing email?

from healthchecks.

Thanks for the quick response! The main reason why we don't want to use email is because not all users have emails in our active directory.

Healthchecks is deployed behind kong api gateway. We have configured the kong request transformer to add the REMOTE_USER_HEADER depending on the user authenticating to kong (we have also configured kong oidc plugin for authentication).

Users are encouraged to configure mattermost notifications instead.

from healthchecks.

I'm not planning to work on this in near term myself, but I will accept a PR which fixes this, if changes are minimal and not disruptive.

from healthchecks.