You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+8-7
Original file line number
Diff line number
Diff line change
@@ -33,19 +33,19 @@ When automatic migration is enabled (`map_legacy_users: true`), Headscale will f
33
33
- If `strip_email_domain: true` (the default): the Headscale username matches the "username" part of their email address.
34
34
- If `strip_email_domain: false`: the Headscale username matches the _whole_ email address.
35
35
36
-
On migration, Headscale will change the account's username to their `preferred_username`. **This could break any ACLs or policies which are configured to match by username.**
36
+
On migration, Headscale will change the account's username to their `preferred_username`. **This could break any ACLs or policies which are configured to match by username.**
37
37
38
-
Like with Headscale v0.23.0 and earlier, this migration only works for users who haven't changed their email address since their last Headscale login.
38
+
Like with Headscale v0.23.0 and earlier, this migration only works for users who haven't changed their email address since their last Headscale login.
39
39
40
-
A _successful_ automated migration should otherwise be transparent to users.
40
+
A _successful_ automated migration should otherwise be transparent to users.
41
41
42
-
Once a Headscale account has been migrated, it will be _unavailable_ to be matched by the legacy process. An OIDC login with a matching username, but _non-matching_`iss` and `sub` will instead get a _new_ Headscale account.
42
+
Once a Headscale account has been migrated, it will be _unavailable_ to be matched by the legacy process. An OIDC login with a matching username, but _non-matching_`iss` and `sub` will instead get a _new_ Headscale account.
43
43
44
-
Because of the way OIDC works, Headscale's automated migration process can _only_ work when a user tries to log in after the update. Mass updates would require Headscale implement a protocol like SCIM, which is **extremely** complicated and not available in all identity providers.
44
+
Because of the way OIDC works, Headscale's automated migration process can _only_ work when a user tries to log in after the update. Mass updates would require Headscale implement a protocol like SCIM, which is **extremely** complicated and not available in all identity providers.
45
45
46
-
Administrators could also attempt to migrate users manually by editing the database, using their own mapping rules with known-good data sources.
46
+
Administrators could also attempt to migrate users manually by editing the database, using their own mapping rules with known-good data sources.
47
47
48
-
Legacy account migration should have no effect on new installations where all users have a recorded `sub` and `iss`.
48
+
Legacy account migration should have no effect on new installations where all users have a recorded `sub` and `iss`.
49
49
50
50
##### What happens when automatic migration is disabled?
51
51
@@ -95,6 +95,7 @@ This will also affect the way you [reference users in policies](https://github.c
95
95
- Fixed missing `stable-debug` container tag [#2232](https://github.com/juanfont/headscale/pr/2232)
96
96
- Loosened up `server_url` and `base_domain` check. It was overly strict in some cases. [#2248](https://github.com/juanfont/headscale/pull/2248)
97
97
- CLI for managing users now accepts `--identifier` in addition to `--name`, usage of `--identifier` is recommended [#2261](https://github.com/juanfont/headscale/pull/2261)
0 commit comments