**Description** Force https:// for redirection URL and update setup guide to reflect. ⚒️ Fixes # **⚙️ Type of change** - [ ] ⚙️ Feature/App addition - [X] 🪛 Bugfix - [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] 🔃 Refactor of current code **🧪 How Has This Been Tested?** **📃 Notes:** Please verify I did this correctly. **✔️ Checklist:** - [X] ⚖️ My code follows the style guidelines of this project - [X] 👀 I have performed a self-review of my own code - [ ] #️⃣ I have commented my code, particularly in hard-to-understand areas - [X] 📄 I have made corresponding changes to the documentation - [ ] ⚠️ My changes generate no new warnings - [ ] 🧪 I have added tests to this description that prove my fix is effective or that my feature works - [X] ⬆️ I increased versions for any altered app according to semantic versioning **➕ App addition** If this PR is an app addition please make sure you have done the following. - [ ] 🪞 I have opened a PR on [truecharts/containers](https://github.com/truecharts/containers) adding the container to TrueCharts mirror repo. - [ ] 🖼️ I have added an icon in the Chart's root directory called `icon.png` --- _Please don't blindly check all the boxes. Read them and only check those that apply. Those checkboxes are there for the reviewer to see what is this all about and the status of this PR with a quick glance._
5.7 KiB
Authelia + LLDAP + Traefik ForwardAuth Setup guide
This quick guide should take you through the steps necessary to setup Authelia as your forwardAuth for Traefik. We'll be using LLDAP as the backend for Authelia since it's lightweight and simple enough for most users. A more complete video is available on our YouTube Channel
Prerequisites
- Traefik installed (enable the
enterprise train) - Clusterissuer for certificates
- CloudnativePG operator (enable the
operators train)
Setup LLDAP
:::warning
LLDAP is a Stable train chart and therefore isn't supported at the same level as the charts in the Enterprise train (Authelia and Traefik).
:::
- Follow the steps included in the Installation Notes for LLDAP. Pretty straightforward. Change
dc=example,dc=comto your domain, i.e.dc=MYDOMAIN,dc=netand then change your password. Also make sure you have theOperatorstrain enabled andCloudnativePGoperator installed, since you'll need it forLLDAPandAuthelia
-
I've set the services to
ClusterIPsince I'll be using ingress -
Once in
LLDAP, create a user inside thelldap_password_managergroup and change your defaultadminpassword. Thatlldap_password_manageruser will be used to bind toAuthelia. I've created a user calledSteven
Setup Authelia
- The setup for Authelia is very specific, and the logs won't tell you where you've messed up, but there's precise steps used to integrate
LLDAPintoAuthelia. The info comes from the LLDAP Authelia Docs and the upstream repo.
App Configuration
- Domain:
mydomain.com<- Your domain without https:// - Default Redirection URL:
https://auth.mydomain.com<- Can be anything, but we'll stick to auth.mydomain.com. As well, this will be the ingress URL forAuthelia
LDAP Backend Configuration
Click Enable then ensure everything is as below or you won't be able to connect to the LLDAP backend
- Implementation:
Custom(that's the default) - URL:
ldap://lldap-ldap.ix-lldap.svc.cluster.local:3890 - Connection Timeout: 5s
- Start TLS: (Not necessary)
- TLS Settings: (Not necessary)
- Server Name: Leave blank
- Skip Certificate Verification: Leave unchecked
- Minimum TLS version:
TLS1.2 - Base DN:
DC=mydomain,DC=com - Username Attribute:
uid - Additional Users DN:
ou=people - Users Filter:
(&(|({username_attribute}={input})({mail_attribute}={input}))(objectClass=person)) - Additional Groups DN:
ou=groups - Groups Filter:
(member={dn}) - Group name Attribute:
cn - Mail Attribute:
mail - Display Name Attribute:
displayName - Admin User:
uid=Steven,ou=people,dc=mydomain,dc=com<- Notice the uid=Steven, most of the time people use admin and a generated password - Password:
RANDOMPASSWORD
SMTP Configuration
Check your mail provider for this, generally Gmail gives you an app specific password for your email account and uses smtp.gmail.com and port 587
Access Control Configuration
- This section is to set rules to connect to
Autheliaand which users can go where. This is a basic general rule below where the main user (Steven) can access all the site using a wildcard
Leave the default one_factor unless you've setup TOTP above. Then click Add next to Rules to get the screen below
- Add your
Domainand aWildcardfor your subdomains. - Leave policy
one_factor - Click
Add Subjectand add a subject ofgroup:lldap_password_managersinceStevenis part of that group
Setup Authelia Ingress
- Make sure you're using the same domain as the
Default Redirection URLabove, so for me that'sauth.mydomain.com
Traefik ForwardAuth Setup
-
This part is straight forward as long as you have a working
Traefikinstall, please see our How-To if you need more info on getting that running. -
Scroll down to
forwardAuthand clickAdd
- Name your
forwardauthsomething you'll remember, since that's the middleware you'll add to your ingress going forward. Most people useauth - Address:
http://authelia.ix-authelia.svc.cluster.local:9091/api/verify?rd=https://auth.mydomain.com/and replace the last part based onmydomain.com, and if you've changed ports/names you can get that fromHeavyscript - Check
trustForwardHeader - Add the following
authResponseHeaders(pressAdd4 times)Remote-UserRemote-GroupRemote-NameRemote-Email
Adding the forwardauth to your Apps
The last step is adding the forwardauth along with the standard ingress settings for your app, for more info on setting ingress see the ClusterIssuer Guide. What changes versus a standard setup is the Traefik Middlewares section, where you must add your forwardauth to the section.
- In this example we use the same name as above, or
auth. ClickAddto theTraefik Middlewaressection, and enter yourforwardauthname.
References
The origin material for this guide is available on the LLDAP Github. While further information on Authelia can be found on their Github and website.
Support
If you have any issues with following this guide, we can be reached using Discord for real-time feedback and support.




