From 8c79e6beca63a818a2041f6f16275374626f0ae9 Mon Sep 17 00:00:00 2001 From: Amir Zarrinkafsh Date: Fri, 12 Feb 2021 14:00:36 +1100 Subject: [PATCH] ci(buildkite): utilise conventional-changelog for release notes (#1714) Instead of generating our changelog based on crude modifications utilising git log we now utilise conventional-changelog. conventional-changelog utilises the angular commit structure to categorise and display the changelog for 3 types (fix,feat,perf) and each of the change scopes are identified in the changelog too. An example of the output for v4.26.0 can be found below: # [4.26.0](https://github.com/authelia/authelia/compare/v4.25.2...v4.26.0) (2021-02-02) ### Bug Fixes * **handlers:** refresh user details on all domains ([#1642](https://github.com/authelia/authelia/issues/1642)) ([60ff16b](https://github.com/authelia/authelia/commit/60ff16b518e54bcc2cbb7a3a3441c47b1d382be6)) ### Docker Container * `docker pull authelia/authelia:4.26.0` --- .buildkite/deployment.sh | 4 +- .buildkite/pipeline.sh | 4 +- .buildkite/steps/ghartifacts.sh | 2 +- BREAKING.md | 193 -------------------------------- README.md | 4 +- 5 files changed, 8 insertions(+), 199 deletions(-) delete mode 100644 BREAKING.md diff --git a/.buildkite/deployment.sh b/.buildkite/deployment.sh index 22fc75c4c..70fa3512a 100755 --- a/.buildkite/deployment.sh +++ b/.buildkite/deployment.sh @@ -6,9 +6,9 @@ DIVERGED=$(git merge-base --fork-point origin/master > /dev/null; echo $?) if [[ $DIVERGED == 0 ]]; then if [[ $BUILDKITE_TAG == "" ]]; then if [[ $BUILDKITE_BRANCH == "master" ]]; then - CI_BYPASS=$(git diff --name-only HEAD~1 | sed -rn '/^(BREAKING.md|CONTRIBUTING.md|README.md|SECURITY.md|\.all-contributorsrc|docs\/.*)/!{q1}' && echo true || echo false) + CI_BYPASS=$(git diff --name-only HEAD~1 | sed -rn '/^(CONTRIBUTING.md|README.md|SECURITY.md|\.all-contributorsrc|docs\/.*)/!{q1}' && echo true || echo false) else - CI_BYPASS=$(git diff --name-only `git merge-base --fork-point origin/master` | sed -rn '/^(BREAKING.md|CONTRIBUTING.md|README.md|SECURITY.md|\.all-contributorsrc|docs\/.*)/!{q1}' && echo true || echo false) + CI_BYPASS=$(git diff --name-only `git merge-base --fork-point origin/master` | sed -rn '/^(CONTRIBUTING.md|README.md|SECURITY.md|\.all-contributorsrc|docs\/.*)/!{q1}' && echo true || echo false) fi else CI_BYPASS="false" diff --git a/.buildkite/pipeline.sh b/.buildkite/pipeline.sh index c11c51f02..da245332f 100755 --- a/.buildkite/pipeline.sh +++ b/.buildkite/pipeline.sh @@ -6,9 +6,9 @@ DIVERGED=$(git merge-base --fork-point origin/master > /dev/null; echo $?) if [[ $DIVERGED == 0 ]]; then if [[ $BUILDKITE_TAG == "" ]]; then if [[ $BUILDKITE_BRANCH == "master" ]]; then - CI_BYPASS=$(git diff --name-only HEAD~1 | sed -rn '/^(BREAKING.md|CONTRIBUTING.md|README.md|SECURITY.md|\.all-contributorsrc|docs\/.*)/!{q1}' && echo true || echo false) + CI_BYPASS=$(git diff --name-only HEAD~1 | sed -rn '/^(CONTRIBUTING.md|README.md|SECURITY.md|\.all-contributorsrc|docs\/.*)/!{q1}' && echo true || echo false) else - CI_BYPASS=$(git diff --name-only `git merge-base --fork-point origin/master` | sed -rn '/^(BREAKING.md|CONTRIBUTING.md|README.md|SECURITY.md|\.all-contributorsrc|docs\/.*)/!{q1}' && echo true || echo false) + CI_BYPASS=$(git diff --name-only `git merge-base --fork-point origin/master` | sed -rn '/^(CONTRIBUTING.md|README.md|SECURITY.md|\.all-contributorsrc|docs\/.*)/!{q1}' && echo true || echo false) fi if [[ $CI_BYPASS == "true" ]]; then diff --git a/.buildkite/steps/ghartifacts.sh b/.buildkite/steps/ghartifacts.sh index 90a375b7a..1f3d44072 100755 --- a/.buildkite/steps/ghartifacts.sh +++ b/.buildkite/steps/ghartifacts.sh @@ -13,7 +13,7 @@ do done echo "--- :github: Deploy artifacts for release: ${BUILDKITE_TAG}" -hub release create "${BUILDKITE_TAG}" "${artifacts[@]}" -F <(echo -e "${BUILDKITE_TAG}\n\n$(awk "/${BUILDKITE_TAG}/" RS="## Breaking" BREAKING.md)\n\n## Changelog\n$(git log --oneline --pretty='* %h %s' $(git describe --abbrev=0 --tags $(git rev-list --tags --skip=1 --max-count=1))...$(git describe --abbrev=0 --tags))\n\n## Docker Container\n* \`docker pull authelia/authelia:${BUILDKITE_TAG//v}\`" | sed -e 's/^ /## Breaking /' | sed -e '/./b' -e :n -e 'N;s/\n$//;tn'); EXIT=$? +hub release create "${BUILDKITE_TAG}" "${artifacts[@]}" -F <(echo -e "${BUILDKITE_TAG}\n$(conventional-changelog -p angular -o /dev/stdout -r 2 | sed -e '1,3d')\n\n### Docker Container\n* \`docker pull authelia/authelia:${BUILDKITE_TAG//v}\`"); EXIT=$? if [[ $EXIT == 0 ]]; then diff --git a/BREAKING.md b/BREAKING.md deleted file mode 100644 index 9eec2fe03..000000000 --- a/BREAKING.md +++ /dev/null @@ -1,193 +0,0 @@ -Breaking changes -================ - -Since Authelia is still under active development, it is subject to breaking changes. It's -recommended not to use the 'latest' Docker image tag blindly but pick a version instead -and read this documentation before upgrading. This is where you will get information about -breaking changes and about what you should do to overcome those changes. - -## Breaking in v4.25.0 - -### Deprecation Notice(s) -* All of these deprecations will be fully removed in release 4.28.0 -* The SMTP notifiers `trusted_cert` option has been deprecated (replaced by global certificates_directory) -* The SMTP notifiers `disable_verify_cert` option has been deprecated (replaced by `notifier.smtp.tls.skip_verify`) -* The LDAP authentication backends `skip_verify` option has been deprecated (replaced by `authentication_backend.ldap.tls.skip_verify`) -* The LDAP authentication backends `minimum_tls_version` option has been deprecated (replaced by `authentication_backend.ldap.tls.minimum_version`) - -Examples can be found in the documentation for the new [shared TLS config](https://www.authelia.com/docs/configuration/#tls-configuration), -for the [LDAP authentication backend](https://www.authelia.com/docs/configuration/authentication/ldap.html), and for the -[SMTP notifier backend](https://www.authelia.com/docs/configuration/notifier/smtp.html). - -## Breaking in v4.24.0 - -### Deprecation Notice(s) -* LDAP User Provider Filters (final removal in 4.28.0): - * User Filters containing `{0}` are being deprecated and will generate warnings. Replaced with `{input}`. - * Group Filters containing `{0}` or `{1}` are being deprecated and will generate warnings. - Replaced with `{input}` and `{username}` respectively. - -## Breaking in v4.21.0 -* New LDAP attribute `display_name_attribute` has been introduced, defaults to value: `displayname`. -* New key `displayname` has been introduced into the file based user database. - -These are utilised to greet the logged in user. - -If utilising a file based user backend: -* Administrators will need to update users and include the `displayname` key. - -**Before:** -```yaml -users: - john: - password: "$6$rounds=500000$jgiCMRyGXzoqpxS3$w2pJeZnnH8bwW3zzvoMWtTRfQYsHbWbD/hquuQ5vUeIyl9gdwBIt6RWk2S6afBA0DPakbeWgD/4SZPiS0hYtU/" - email: john.doe@authelia.com - groups: - - admins - - dev -``` -**After:** -```yaml -users: - john: - displayname: "John Doe" - password: "$6$rounds=500000$jgiCMRyGXzoqpxS3$w2pJeZnnH8bwW3zzvoMWtTRfQYsHbWbD/hquuQ5vUeIyl9gdwBIt6RWk2S6afBA0DPakbeWgD/4SZPiS0hYtU/" - email: john.doe@authelia.com - groups: - - admins - - dev -``` -* Users with long-lived sessions will need to recreate the session (logout and login) to propagate the changes. - -## Breaking in v4.20.0 -* Authelia's Docker volumes have been refactored. All data should reside within a single volume of `/config`. -All examples have been updated to reflect this change. The entrypoint for the container changed from -`authelia --config /etc/authelia/configuration.yml` to `authelia --config /config/configuration.yml`. - -Users migrating to v4.20.0 have two options: -1. Change your container mappings to point to `/config` also change any associated paths in your `configuration.yml` to -represent the new `/config` mappings. -2. Change your container entry point back to `authelia --config /etc/authelia/configuration.yml` - * **Docker Compose:** `command: authelia --config /etc/authelia/configuration.yml` - * **Docker Run:** `docker run -d -v /path/on/host:/etc/authelia authelia/authelia:latest authelia --config /etc/authelia/configuration.yml` - -The team recommends option 1 to unify/simplify troubleshooting for support related issues. - -## Breaking in v4.18.0 -* Secrets stored directly in ENV are now removed from Authelia. They have been replaced with file -secrets. If you still have not moved feel free to contact the team for assistance, otherwise the -[documentation](https://docs.authelia.com/configuration/secrets.html) has instructions on how to utilize these. - -## Breaking in v4.15.0 -* Previously if a configuration value did not exist we ignored it. Now we will error if someone has -specified either an unknown configuration key or one that has changed. In the instance of a changed -key a more specific error is intended. This may cause some people who have not updated their config -to see new errors. -* Authelia now checks the Notifier is configured correctly before becoming available. If the -SMTP Notifier is used and the configuration is wrong or there is something wrong with the server -Authelia will not start. If the File Notifier is used and the file is not writable Authelia will -not start. -* Authelia v3 migration tools are being removed in this release due to the length of time which -has passed since v4 release. Older versions will still be available for migration if needed. - -### Deprecation Notice(s) -* Environment variable secrets are insecure and have been replaced by a file based alternative -instead of having the plain text secret in the environment variables. In version 4.18.0 the old method -will be completely removed. Read more in the [docs](https://docs.authelia.com/configuration/secrets.html). - -## Breaking in v4.10.0 -* Revert of `users_filter` purpose. This option now represents the complete search filter again, meaning -there is no more automatic filter computation based on username. This gives the most flexibility. -For instance, this allows administrators to choose whether they want the users to be able to sign in with -username or email. - -## Breaking in v4.7.0 -* `logs_level` configuration key has been renamed to `log_level`. -* `users_filter` was a search pattern for a given user with the `{0}` matcher replaced with the -actual username. In v4.7.0, `username_attribute` has been introduced. Consequently, the computed -user filter utilised by the LDAP search query is a combination of filters based on the -`username_attribute` and `users_filter`. `users_filter` now reduces the scope of users targeted by -the LDAP search query. For instance if `username_attribute` is set to `uid` and `users_filter` is -set to `(objectClass=person)` then the computed filter is `(&(uid=john)(objectClass=person))`. - -## Breaking in v4.0.0 -Authelia has been rewritten in Go for better code maintainability and for performance and -security reasons. - -The principles stay the same, Authelia is still an authenticating and authorizing proxy. -Some major changes have been made though so 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. - -### 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 removed and replaced with a Browser router. This means that the weird characters -/%23/ and /#/ in the redirection URL can 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) -supported by Authelia v4. - -Example of usage: -``` -# Migrate a local database into the targeted database defined in config-v4.yml with Docker -docker run --rm -v /path/to/config-v4.yml:/config.yml -v /old/db/path:/db authelia/authelia:4.14.2 authelia migrate local --config=/config.yml --db-path=/db - -# Migrate a mongo database into the targeted database defined in config-v4.yml with Docker -docker run --rm -v /path/to/config-v4.yml:/config.yml authelia/authelia:4.14.2 authelia migrate mongo --config=/config.yml --url=mongodb://myuser:mypassword@mymongo:27017 --database=authelia -``` - -Those commands migrate TOTP secrets, U2F devices, authentication traces and user preferences so -that the migration is almost seamless for your users. - -The identity verification tokens are not migrated though since their format has changed. However they were -made to expire after a few minutes anyway. Consequently, the users who initiated a device registration process -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. - -## Breaking in v3.14.0 - -### Headers in nginx configuration -In order to support Traefik as a third party proxy interacting with Authelia some changes had to be made -to Authelia and the nginx proxy configuration. - -The `Host` header is not used anymore by Authelia in any way. It was previously used to compute the url of the link that is -sent by Authelia for confirming the identity of the user. In the new version X-Forwarded-Proto, X-Forwarded-Host -headers are used to build the URL. - -Authelia endpoint /api/verify does not produce the `Redirect` header containing the target URL the user is trying to visit. -This header was used in early versions to redirect the user to the login portal providing the target URL as a query parameter. -However this target URL can be computed automatically with the following statement: -``` -set $target_url $scheme://$http_host$request_uri; -``` - -## Breaking in v3.11.0 - -### ACL configuration -ACL definition in the configuration file has been updated to allow more authorization use cases. -The change basically removed the three categories "any", "groups" and "users" to introduce an -iptables-like format where the authorization policy is just an ordered list of rules with a few -attributes among which the attribute called `subject` used to map old categories. - -So in order to upgrade from prior version, you simply need to flatten the rules you already have and -use the `subject` attribute to map your rules from the previous categories into the list. For `any` -rules, just don't specify the subject attribute, this rule will then apply to any user. For group-based -rules you can use `subject: 'group:mygroup'` where `mygroup` is the group you set authorizations for. -For user-based rules, use `subject: 'user:myuser'` where `myuser` is the user you set authorizations for. - -Please note that in the new system, the first matching rule applies and the next ones are not taken into -account. If no rule apply, the default policy still applies and if no default policy is provided, the `deny` -policy applies. diff --git a/README.md b/README.md index 86927eb14..26efa52ac 100644 --- a/README.md +++ b/README.md @@ -136,7 +136,9 @@ disclosure related matters. If you need to contact us for another reason please ## Breaking changes -See [BREAKING](./BREAKING.md). +Since Authelia is still under active development, it is subject to breaking changes. +It's recommended to pin a version tag instead of using the `latest` tag and reading the [release notes](https://github.com/authelia/authelia/releases) before upgrading. +This is where you will find information about breaking changes and what you should do to overcome those changes. ## Why Open Source?