11# whawty.auth store sync
22
3- As the whawty.auth store is just a simple directory you may synchronise multiple
3+ As the whawty.auth store is just a simple directory you may synchronize multiple
44instances using rsync. One way to do this is documented here.
55
66## Introduction
77
8- The synchronisation is based on a simple master slave system. The master host is an app
8+ The synchronization is based on a simple master slave system. The master host is an app
99running on one machine which might be configured to do local upgrades (see below). One or
10- more slaves use systemd.timer, rsync and ssh to synchronise the local file store with
10+ more slaves use systemd.timer, rsync and ssh to synchronize the local file store with
1111the one on the (remote) master host.
1212
1313### context upgrades
@@ -16,7 +16,7 @@ The whawty.auth app can be configured to automatically upgrade passwords hashes
1616authenticate against it. For this to work the storage backend compares the current default
1717hashing format and default ` context-id ` , as set by the store configuration, with the one which
1818was used to generate the current hash. If the format or ` context-id ` 's differ it marks the
19- hash as upgradeable . After a successful authentication the app now does one of the following:
19+ hash as upgrade-able . After a successful authentication the app now does one of the following:
2020
2121- ** do nothing:** no upgrade will be done, the hash files will stay untouched
2222- ** local upgrades:** do an update operation on the local store
@@ -82,16 +82,16 @@ hashes from the master using the following command:
8282
8383 # sudo -u whawty-auth rsync -rlptv --delete -e ssh whawty-auth-master::store /var/lib/whawty/auth/store
8484
85- On the first connection you will get asked to accept the ssh fingreprint of the master. If you run
86- the command a second time no errors/warnings shoulb be shown.
87- After that you can enable the synchronisation by copying the files ` whawty-auth-sync.service ` and
85+ On the first connection you will get asked to accept the ssh fingerprint of the master. If you run
86+ the command a second time no errors/warnings should be shown.
87+ After that you can enable the synchronization by copying the files ` whawty-auth-sync.service ` and
8888` whawty-auth-sync.timer ` to ` /etc/systemd/system ` and enabling the timer using the following commands:
8989
9090 # systemctl daemon-reload
9191 # systemctl enable whawty-auth-sync.timer
9292 # systemctl start whawty-auth-sync.timer
9393
94- If you also want to have automatic ` context-id ` upgrades on succesfull logins you need to configure the
94+ If you also want to have automatic ` context-id ` upgrades on successful logins you need to configure the
9595slave to do remote upgrades using the the following as an argument to the ` --do-upgrades ` command line option:
9696
9797 https://whawty-auth-master.example.com/api/update
0 commit comments