Hallucinating Robot

I believe that Hardware tokens work. But then maybe the available options send to the browser need to be limited? I'm not familiar with the implementation of FIDO. Right now,...

So maybe the "phone" option needs to be disabled or something about the implementation needs to be enabled I see some options in this official demo of FIDO: https://webauthn.io/. Maybe...

+1 for hiding the 'Contact support' ability. Or any customizability. And related to https://github.com/greenpau/caddy-security/issues/127.

I didn't disable it but wanted to. What I tried didn't work. For the sake of customizability. I have several use cases where I would only want to use this...

Great, thanks a lot. Is it only disabled in the UI? Therefore, would calling the functions directly still work? As that seems kind of insecure to me.

Thanks. Why a different repo? How are these two repos connected or related?

Those mentioned files are out of sync with the compiled ones. So, it's somewhat unreliable to build something based of that.

https://github.com/androw/docker-caddy-security/blob/main/Dockerfile contains `github.com/greenpau/[email protected]` which is dead (404)? However `docker exec caddy /usr/bin/caddy build-info` does under dependencies contain: ``` github.com/greenpau/caddy-security v1.1.13 h1:0o/cAJVdwGVZxkR8yV91oW7UljISdP9wIv45NSujmiY= github.com/greenpau/go-authcrunch v1.0.34 h1:0Nc3Scbm49chAdIOfHKvKFXYD/gJA6m9/2DYO8Qygmg= github.com/greenpau/versioned v1.0.27 h1:aFJ16tzsUkbc6WT7DRia60S0VrgWzBNuul3h0RXFKxM= ```

## directive 'authenticate' is not ordered ``` http://auth.xxxxx.xx { authenticate * with myportal } ``` ``` {"level":"info","ts":1655547020.1768386,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"} run: adapting config using caddyfile: directive 'authenticate' is not ordered, so...

Done. Getting somewhere. Whats the format or example of users.json?