Compare commits

...

2 Commits

Author SHA1 Message Date
884cd7ae9a ajout auth 2025-01-27 11:58:50 +01:00
a327043c65 Maj Readme 2025-01-27 10:17:00 +01:00
3 changed files with 105 additions and 10 deletions

8
auth/README.md Normal file
View File

@ -0,0 +1,8 @@
# Authelia - on outil d'authentification centralisée 2FA
## Mise en oeuvre
sur une machine disposant de docker et de git :
````shell
````

87
auth/Vagrantfile vendored Normal file
View File

@ -0,0 +1,87 @@
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://vagrantcloud.com/search.
config.vm.box = "debian/bookworm64"
config.vm.hostname= "auth"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# NOTE: This will enable public access to the opened port
# config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine and only allow access
# via 127.0.0.1 to disable public access
# config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network "private_network", ip: "192.168.33.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
config.vm.network "public_network"
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Disable the default share of the current code directory. Doing this
# provides improved isolation between the vagrant box and your host
# by making sure your Vagrantfile isn't accessible to the vagrant box.
# If you use this you may want to enable additional shared subfolders as
# shown above.
# config.vm.synced_folder ".", "/vagrant", disabled: true
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider "virtualbox" do |vb|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
#
# # Customize the amount of memory on the VM:
# vb.memory = "1024"
# end
#
# View the documentation for the provider you are using for more
# information on available options.
# Enable provisioning with a shell script. Additional provisioners such as
# Ansible, Chef, Docker, Puppet and Salt are also available. Please see the
# documentation for more information about their specific syntax and use.
config.vm.provision "shell", inline: <<-SHELL
timedatectl set-timzzone Europe/Paris
apt-get update
apt install -y wget curl git vim
if ! which docker ; then
curl -s -o getdocker.sh https://get.docker.com
bash getdocker.sh
gpasswd -a vagrant docker
fi
git clone https://github.com/authelia/authelia.git
cd authelia
git checkout $(git describe --tags `git rev-list --tags --max-count=1`)
SHELL
end

View File

@ -12,25 +12,25 @@ Cette `Vagrantfile` permet d'installer :
La Vagrantfile utilise les playbooks ansible suivants :
* **provision/setup-stork.yml** qui:
* installe les dépots ISC pour stork
* installe les paquets postgresql, postgresql-contrib, stork-server
* crée la base de données stork et genère le fichiers de configuration storki-server
* relance le service stork-server
* installe les paquets **postgresql**, **postgresql-contrib**, **stork-server**
* crée la base de données stork et genère le fichiers de configuration de **stork-server**
* relance le service **isc-stork-server**
* **provision/setup-kea.yml** qui:
* installe les dépots ISC pour kea
* installe les paquets isc-kea-dhcp4-server, isc-kea-ctrl-agent, isc-kea-hooks
* installe les paquets **isc-kea-dhcp4-server**, **isc-kea-ctrl-agent**, **isc-kea-hooks**
* installe les dépots ISC pour stork
* installe le paquet stork-agent
* installe le paquet **stork-agent**
* genére les fichiers de configuration pour chacun des services
* relance les services
* enregistre (`stork-agent register`) le serveur auprès du serveur stork
## Les services et ports
* serveur **stork** :
* service stork-server:8080
* service **stork-server:8080**
* serveur **kea1** et **kea2** :
* service isc-kea-dhcp4-server:8000 (utilisé par la HA)
* service kea-ctrl-agent:8001
* service isc-stork-agent:8080
* service **isc-kea-dhcp4-server:8000** (utilisé par la HA)
* service **kea-ctrl-agent:8001**
* service **isc-stork-agent:8080**
## Utilisation de la Vagrantfile
@ -39,7 +39,7 @@ La Vagrantfile utilise les playbooks ansible suivants :
vagrant up kea1
vagrant up kea2
````
On peut alors se connecter au serveur **stork** avec un navigateur : http://<adresse>:8080
On peut alors se connecter au serveur **stork** avec un navigateur : http://adresse:8080
(admin/admin)
Une fois connecté, on doit autoriser chacun des deux serveurs **kea1** et **kea2** inscrits