disable_startup_check option is not honored #8975
Description
Version
v4.39.0
Deployment Method
Other
Reverse Proxy
Caddy
Reverse Proxy Version
2.9.1
Description
The option disable_startup_check for the notifiers seems that is not honored anymore. Independently from the values assigned, if any, the startup check is nevertheless executed.
Apparently, the code in internal/middlewares/startup.go seems to confirm that for notifiers the disabled variable is always set to false.
Reproduction
Start Authelia pointing the SMTP notifier to a Microsoft SMTP server, which will fail as Basic Autentication is now disabled and Authelia does not support OAUTH2 currently. Even with:
notifier:
disable_startup_check: true
in the configuration file, the service will fail to start because the startup check is nevertheless run.
Expectations
Startup checking should be disabled.
Configuration (Authelia)
notifier:
disable_startup_check: true
smtp:
address: 'smtp://smtp.office365.com:587'
username: <redacted>
sender: 'Ethereal Authentication Service <redacted>'
identifier: 'localhost'
subject: '[Authelia] {title}'
startup_check_address: <redacted>
disable_require_tls: false
disable_starttls: false
disable_html_emails: false
tls:
server_name: 'smtp.office365.com'
skip_verify: false
minimum_version: 'TLS1.2'
maximum_version: 'TLS1.3'Build Information
Last Tag: v4.39.0
State: tagged clean
Branch: v4.39.0
Commit: bbfa41712ce1b3e39b4798b18bd5f78e68470720
Build Number: 41111
Build OS: linux
Build Arch: amd64
Build Compiler: gc
Build Date: Sun, 16 Mar 2025 21:05:57 +1100
Extra:
Go:
Version: go1.24.1
Module Path: github.com/authelia/authelia/v4
Executable Path: github.com/authelia/authelia/v4/cmd/autheliaLogs (Authelia)
time="2025-03-16T15:33:58+01:00" level=debug msg="Registering OpenID Connect 1.0 client with client id 'bookstack' and policy 'one_factor'"
time="2025-03-16T15:33:58+01:00" level=debug msg="Registering OpenID Connect 1.0 client with client id 'gitea' and policy 'one_factor'"
time="2025-03-16T15:33:58+01:00" level=debug msg="Registering OpenID Connect 1.0 client with client id 'minio' and policy 'one_factor'"
time="2025-03-16T15:33:58+01:00" level=debug msg="Registering OpenID Connect 1.0 client with client id 'portainer' and policy 'one_factor'"
time="2025-03-16T15:33:58+01:00" level=debug msg="Registering OpenID Connect 1.0 client with client id 'proxmox' and policy 'one_factor'"
time="2025-03-16T15:33:58+01:00" level=debug msg="Registering OpenID Connect 1.0 client with client id 'jellyfin' and policy 'one_factor'"
time="2025-03-16T15:33:58+01:00" level=info msg="Storage schema is being checked for updates"
time="2025-03-16T15:33:58+01:00" level=info msg="Storage schema is already up to date"
time="2025-03-16T15:33:58+01:00" level=debug msg="LDAP Supported OIDs. Control Types: none. Extensions: 1.3.6.1.4.1.4203.1.11.1"
time="2025-03-16T15:34:09+01:00" level=error msg="Error occurred running a startup check" error="failed to dial connection: SMTP AUTH failed: 535 5.7.139 Authentication unsuccessful, basic authentication is disabled. [MA4P292CA0002.ESPP292.PROD.OUTLOOK.COM 2025-03-16T14:34:04.556Z 08DD63756EE3076F]" provider=notification stack="github.com/authelia/authelia/v4/internal/middlewares/startup.go:70 doStartupCheck\ngithub.com/authelia/authelia/v4/internal/middlewares/startup.go:26 (*Providers).StartupChecks\ngithub.com/authelia/authelia/v4/internal/commands/root.go:90 (*CmdCtx).RootRunE\ngithub.com/spf13/cobra@v1.9.1/command.go:1015 (*Command).execute\ngithub.com/spf13/cobra@v1.9.1/command.go:1148 (*Command).ExecuteC\ngithub.com/spf13/cobra@v1.9.1/command.go:1071 (*Command).Execute\ngithub.com/authelia/authelia/v4/cmd/authelia/main.go:10 main\ninternal/runtime/atomic/types.go:194 (*Uint32).Load\nruntime/asm_amd64.s:1700 goexit"Logs (Proxy / Application)
Documentation
No response
Generative AI
No
Pre-Submission Checklist
-
I agree to follow the Code of Conduct
-
This is a bug report and not a support request
-
I have read the security policy and this bug report is not a security issue or security related issue
-
I have either included the complete configuration file or I am sure it's unrelated to the configuration
-
I have either included the complete debug / trace logs or the output of the build-info command if the logs are not relevant
-
I have provided all of the required information in full with the only alteration being reasonable sanitization in accordance with the Troubleshooting Sanitization reference guide
-
I have checked for related proxy or application logs and included them if available
-
I have checked for related issues and checked the documentation