From 8c7e65061649c62a5323ad13d6067daa4e34734b Mon Sep 17 00:00:00 2001 From: nblock Date: Tue, 13 May 2025 20:38:52 +0200 Subject: [PATCH] Remove map_legacy_users from example configuration (#2590) --- config-example.yaml | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/config-example.yaml b/config-example.yaml index edd0586d..b62ca02e 100644 --- a/config-example.yaml +++ b/config-example.yaml @@ -375,19 +375,6 @@ unix_socket_permission: "0770" # # - plain: Use plain code verifier # # - S256: Use SHA256 hashed code verifier (default, recommended) # method: S256 -# -# # Map legacy users from pre-0.24.0 versions of headscale to the new OIDC users -# # by taking the username from the legacy user and matching it with the username -# # provided by the OIDC. This is useful when migrating from legacy users to OIDC -# # to force them using the unique identifier from the OIDC and to give them a -# # proper display name and picture if available. -# # Note that this will only work if the username from the legacy user is the same -# # and there is a possibility for account takeover should a username have changed -# # with the provider. -# # When this feature is disabled, it will cause all new logins to be created as new users. -# # Note this option will be removed in the future and should be set to false -# # on all new installations, or when all users have logged in with OIDC once. -# map_legacy_users: false # Logtail configuration # Logtail is Tailscales logging and auditing infrastructure, it allows the control panel