6
6
7
7
- ` oidc.map_legacy_users ` is now ` false ` by default
8
8
[ #2350 ] ( https://github.com/juanfont/headscale/pull/2350 )
9
+ - Print Tailscale version instead of capability versions for outdated nodes
10
+ [ #2391 ] ( https://github.com/juanfont/headscale/pull/2391 )
9
11
10
12
## 0.24.2 (2025-01-30)
11
13
24
26
[ #2367 ] ( https://github.com/juanfont/headscale/pull/2367 )
25
27
- Relax username validation to allow emails
26
28
[ #2364 ] ( https://github.com/juanfont/headscale/pull/2364 )
27
- - Remove invalid routes and add stronger constraints for routes to avoid API panic
28
- [ #2371 ] ( https://github.com/juanfont/headscale/pull/2371 )
29
+ - Remove invalid routes and add stronger constraints for routes to avoid API
30
+ panic [ #2371 ] ( https://github.com/juanfont/headscale/pull/2371 )
29
31
- Fix panic when ` derp.update_frequency ` is 0
30
32
[ #2368 ] ( https://github.com/juanfont/headscale/pull/2368 )
31
33
@@ -60,8 +62,7 @@ and have it populate to Headscale automatically the next time they log in.
60
62
However, this may affect the way you reference users in policies.
61
63
62
64
Headscale v0.23.0 and earlier never recorded the ` iss ` and ` sub ` fields, so all
63
- legacy (existing) OIDC accounts _ need to be migrated_ to be properly
64
- secured.
65
+ legacy (existing) OIDC accounts _ need to be migrated_ to be properly secured.
65
66
66
67
#### What do I need to do to migrate?
67
68
@@ -73,8 +74,8 @@ The migration will mostly be done automatically, with one exception. If your
73
74
OIDC does not provide an ` email_verified ` claim, Headscale will ignore the
74
75
` email ` . This means that either the administrator will have to mark the user
75
76
emails as verified, or ensure the users verify their emails. Any unverified
76
- emails will be ignored, meaning that the users will get new accounts instead
77
- of being migrated.
77
+ emails will be ignored, meaning that the users will get new accounts instead of
78
+ being migrated.
78
79
79
80
After this exception is ensured, make all users log into Headscale with their
80
81
account, and Headscale will automatically update the account record. This will
@@ -175,7 +176,8 @@ This will also affect the way you
175
176
- User gRPC/API [ #2261 ] ( https://github.com/juanfont/headscale/pull/2261 ) :
176
177
- If you depend on a Headscale Web UI, you should wait with this update until
177
178
the UI have been updated to match the new API.
178
- - ` GET /api/v1/user/{name} ` and ` GetUser ` have been removed in favour of ` ListUsers ` with an ID parameter
179
+ - ` GET /api/v1/user/{name} ` and ` GetUser ` have been removed in favour of
180
+ ` ListUsers ` with an ID parameter
179
181
- ` RenameUser ` and ` DeleteUser ` now require an ID instead of a name.
180
182
181
183
### Changes
@@ -197,9 +199,12 @@ This will also affect the way you
197
199
- CLI for managing users now accepts ` --identifier ` in addition to ` --name ` ,
198
200
usage of ` --identifier ` is recommended
199
201
[ #2261 ] ( https://github.com/juanfont/headscale/pull/2261 )
200
- - Add ` dns.extra_records_path ` configuration option [ #2262 ] ( https://github.com/juanfont/headscale/issues/2262 )
201
- - Support client verify for DERP [ #2046 ] ( https://github.com/juanfont/headscale/pull/2046 )
202
- - Add PKCE Verifier for OIDC [ #2314 ] ( https://github.com/juanfont/headscale/pull/2314 )
202
+ - Add ` dns.extra_records_path ` configuration option
203
+ [ #2262 ] ( https://github.com/juanfont/headscale/issues/2262 )
204
+ - Support client verify for DERP
205
+ [ #2046 ] ( https://github.com/juanfont/headscale/pull/2046 )
206
+ - Add PKCE Verifier for OIDC
207
+ [ #2314 ] ( https://github.com/juanfont/headscale/pull/2314 )
203
208
204
209
## 0.23.0 (2024-09-18)
205
210
@@ -730,8 +735,8 @@ behaviour.
730
735
- All machines can communicate with all machines by default
731
736
- Tags should now work correctly and adding a host to Headscale should now
732
737
reload the rules.
733
- - The documentation have a [fictional example](./docs/ref/acls.md) that should cover
734
- some use cases of the ACLs features
738
+ - The documentation have a [fictional example](./docs/ref/acls.md) that should
739
+ cover some use cases of the ACLs features
735
740
736
741
# ## Features
737
742
@@ -749,7 +754,8 @@ behaviour.
749
754
750
755
- Add IPv6 support to the prefix assigned to namespaces
751
756
- Add API Key support
752
- - Enable remote control of `headscale` via CLI [docs](./docs/ref/remote-cli.md)
757
+ - Enable remote control of `headscale` via CLI
758
+ [docs](./docs/ref/remote-cli.md)
753
759
- Enable HTTP API (beta, subject to change)
754
760
- OpenID Connect users will be mapped per namespaces
755
761
- Each user will get its own namespace, created if it does not exist
0 commit comments