From 2b544346f3a3ba4450d6dd2b2614b51175e712f3 Mon Sep 17 00:00:00 2001 From: Clement Michaud Date: Thu, 5 Dec 2019 21:57:42 +0100 Subject: [PATCH] Update BREAKING.md and CHANGELOG.md --- BREAKING.md | 29 ++++++++++++++++++----------- CHANGELOG.md | 1 + 2 files changed, 19 insertions(+), 11 deletions(-) diff --git a/BREAKING.md b/BREAKING.md index 49c51483..f45460c2 100644 --- a/BREAKING.md +++ b/BREAKING.md @@ -13,7 +13,24 @@ The principles stay the same, Authelia is still an authenticating and authorizin that the system is more reliable overall. This induced breaking the previous data model and the configuration to bring new features but fortunately migration tools are provided to ease the task. -### Migration tools +### Major updates + +* The configuration mostly remained the same, only one major key has been added: `jwt_secret` +and one key removed: `secure` from the SMTP notifier as the Go SMTP library default to TLS +if available. +* The Hash router has been replaced by a Browser router. This means that the weird characters +/%23/ in the URL could now be safely removed. +* The local storage used for dev purpose was a `nedb` database which was implementing the +same interface as mongo but was not really standard. It has been replaced by a good old +sqlite3 database. +* The model of the database is not compatible with v3. This has been decided to better fit +with Golang libraries. +* Some features have been upgraded such as U2F in order to use the latest security features +available like allowing device cloning detection. +* Furthermore, a top-notch web server implementation (fasthttp) has been selected to allow a +large performance gain in order to use Authelia in demanding environments. + +### Data migration tools An authelia-scripts command is provided to perform the data model migration from a local database or a mongo database created by Authelia v3 into a target SQL database (sqlite3, mysql, postgres) @@ -36,16 +53,6 @@ made to expire after a few minutes anyway. Consequently, the users who initiated which has not been completed before the migration will have to restart the device registration process for their device. This is because their identity verification token will not be usable in v4. -### Major changes in details: - -* The configuration mostly remained the same, only one major key has been added: `jwt_secret` and one key removed: `secure` from the -SMTP notifier as the Go SMTP library default to TLS if available. -* The local storage used for dev purpose was a `nedb` database which was implementing the same interface -as mongo but was not really standard. It has been replaced by a good old sqlite3 database. -* The model of the database is not compatible with v3. This has been decided to better fit with Golang libraries. -* Some features have been upgraded such as U2F in order to use the latest security features available like allowing device cloning detection. -* Furthermore, a top-notch web server implementation (fasthttp) has been selected to allow a large performance gain in order to use Authelia in demanding environments. - ## Breaking in v3.14.0 ### Headers in nginx configuration diff --git a/CHANGELOG.md b/CHANGELOG.md index 0d92f067..2f8f9f04 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,7 @@ Release Notes - Version 4.0.0 ------------------------------ * Authelia is rewritten in Go. +* Authelia frontend has been rewritten with Material-UI and simplified. * config.yml should include a secret for jwt issuance and verification. * Models in database have been updated to better fit with the Go library. * The local storage has been replaced by a good old sqlite3 database.