feat!: Use Authelia authentication to protect endpoints
- Uses Authelia as an authentication middleware and access control, with sensible policy - Redis as Authelia's backend for session data - Add https-proto middleware - Add/update example files
This commit is contained in:
39
authelia/users_database.example.yml
Normal file
39
authelia/users_database.example.yml
Normal file
@@ -0,0 +1,39 @@
|
||||
# Authelia User Database
|
||||
# Documentation: https://www.authelia.com/configuration/security/authentication/file/
|
||||
|
||||
# To add users:
|
||||
# 1. Generate a password hash:
|
||||
# docker run authelia/authelia:latest authelia hash-password 'your_strong_password'
|
||||
# 2. Add the user entry below.
|
||||
#
|
||||
# To approve registered users (if registration is enabled in configuration.yml):
|
||||
# 1. New users will appear here, possibly commented out or with 'disabled: true'.
|
||||
# 2. Uncomment the user or set 'disabled: false' to grant access.
|
||||
|
||||
users:
|
||||
# First user is typically considered the admin in access rules
|
||||
admin:
|
||||
displayname: "Admin User"
|
||||
# Replace this hash with one generated for your desired password!
|
||||
password: "$argon2id$v=19$m=102400,t=1,p=8$PBf/L9l3s7LwN6jX/B3tVg$9+q3kL8VAbpWj9Gv9Z6uA5bA4zT1fB2fH3aD5c6b7e8" # Example hash for 'password'
|
||||
email: admin@example.com
|
||||
groups:
|
||||
- admins
|
||||
- users
|
||||
|
||||
# Example of a regular user
|
||||
# user1:
|
||||
# displayname: "Regular User"
|
||||
# password: "..." # Generate hash
|
||||
# email: user1@example.com
|
||||
# groups:
|
||||
# - users
|
||||
|
||||
# Example of a registered user waiting for approval (if registration enabled)
|
||||
# newuser:
|
||||
# disabled: true
|
||||
# displayname: "New User"
|
||||
# password: "..." # Hash generated during registration
|
||||
# email: newuser@example.com
|
||||
# groups:
|
||||
# - users
|
||||
Reference in New Issue
Block a user