Uptime Kuma with local authentication and API turned off - Home Assistant uptime kuma integration does not work without API key #1928
Replies: 2 comments 2 replies
-
|
🏷️ I've automatically added the |
Beta Was this translation helpful? Give feedback.
-
|
The Authentik documentation explicitly instructs users to disable Uptime Kuma’s built-in authentication and rely entirely on SSO handled by the reverse proxy. I'm afraid that the option to disable token passing won't solve your problem. If we wanted the Home Assistant Uptime Kuma integration to support this setup, the integration would need to implement authentication against Authentik itself. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Integration name
Uptime Kuma Integration
Link to integration documentation on our website
https://www.home-assistant.io/integrations/uptime_kuma
Describe the enhancement
I have uptime Kuma installed on my local network and had it integrated with home assistant using the home assistant integration using an API key I generated from the uptime kuma settings interface.
Recently, I have been moving all my home services over to a centralized SSO (Authentik). The Authentik integration instructions directed me to disable local authentication in uptime kuma (settings - advanced disable authentication) and proxy connections to it through Authentik. I have built bypasses for API calls through the authentik provider configuration. I should not need an API key. I am not able to disable the API key requirement in the Uptime Kuma integration. Is this a setting that can be added?
Use cases
Users that are not forcing authentication in uptime kuma are unable to use the integration.
Anything else?
Authentik Uptime Kuma integration instructions: https://integrations.goauthentik.io/monitoring/uptime-kuma/#uptime-kuma-configuration
Beta Was this translation helpful? Give feedback.
All reactions