Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide an option to use default login dashboard #488

Closed
thomaspetit opened this issue Jan 14, 2024 · 1 comment
Closed

Provide an option to use default login dashboard #488

thomaspetit opened this issue Jan 14, 2024 · 1 comment

Comments

@thomaspetit
Copy link

thomaspetit commented Jan 14, 2024

Problem/Motivation

Currently the login page of adguard has been "overriden" in favor of integrating with the user management system of Home Assistant. For 99% of the people I think that this is enough. Sadly it doesn't allow me to integrate this adguard instance within my Kubernetes cluster.

The external-dns application running in my kubernetes cluster(s) allow me to update an adguard instance so that new DNS records are automatically published. For this application to work you either need to use unauthenticated or authenticated access. The latter will use the built-in Adguard login screen.

Actual behavior

We can only set leave_front_door_open or use the built-in authentication mechanism implemented with Home Assistant

Proposed changes

Provide an option to use the built-in login by Adguard (non-default option) on top of the leave_front_door_open feature

@sinclairpaul
Copy link
Member

Nothing has been "overridden" the AdGuard auth isn't configured because it is handled by the reverse proxy in front of it (I don't believe Adguards default is to configure auth).

As it is driven by configuration of the json, how would users then configure it?, it isn't something that the addon needs.

I don't really understand why the auth should be required for the external-dns provider, adguard can run without it. I'd also ask if the addon doesn't meet your needs why wouldn't you just run it in k8s anyway?

@sinclairpaul sinclairpaul closed this as not planned Won't fix, can't repro, duplicate, stale Jan 14, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Feb 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants