thielj

@Crowley723 Sounds good. Not sure if separating is necessary considering that Authelia or upstream LDAP servers can be substantially loaded with just auth requests requiring secure hashes etc. Here's an...

A positive readiness check is by no means a guarantee that everything will work in the near future, as much as a negative result doesn't mean that all requests will...

All services used by Authelia (including DNS availability and DNS individual DNS records, DB, LDAP, Redis, container, VMs, networking, ...) and provided by Authelia (frontend, APIs and auth flows) are...

Sorry, I should have been more precise. Currently, there's just a warning in the log. I wouldn't want to see this turn into a hard error someday, or see non-standard...

@holmanb Nothing exciting really, just the ability to add a custom section that isn't going to disappear or cause conflicts in a future cloud-init release. ``` x-ourstuff: my_machine_id: f18f1218-d8be-4c4d-92c0-bf1703d4e135a cifs:...

@AkshayRao27 - are you aware that there are already LLDAP and PocketID community scripts for a Proxmox LXC setup? If there are any problems with these, it might be worth...

This is normally implemented on the LDAP client side, by searching both the username and the email. Authelia for example uses these defaults for LLDAP: "(&(|({username_attribute}={input})({mail_attribute}={input}))(objectClass=person))" https://github.com/authelia/authelia/blob/6601a20748eb3cfc85352f8ae03d99c58fd24f99/internal/configuration/schema/authentication.go#L350