Skip to content

tsidp-server: add warning for -use-local-tailscaled flag#171

Merged
mostlygeek merged 1 commit into
mainfrom
mg/local-tailscaled-warn
May 21, 2026
Merged

tsidp-server: add warning for -use-local-tailscaled flag#171
mostlygeek merged 1 commit into
mainfrom
mg/local-tailscaled-warn

Conversation

@mostlygeek
Copy link
Copy Markdown
Contributor

When -use-local-tailscaled is true show this warning:

$ go run ./tsidp-server.go --use-local-tailscaled 

┌─[ IMPORTANT WARNING ]────────────────────────────────────────────────────┐
│                                                                          │
│  -use-local-tailscaled is for development only.                          │
│                                                                          │
│  Do not use it in production deployments.                                │
│                                                                          │
└──────────────────────────────────────────────────────────────────────────┘

When using the local tailscaled client tsidp will push a serve configuration into the local tailscaled. This is convenient for development but is not secure enough for production use. For production the recommended path is for tsidp to use the tsnet.Server route and register itself as a separate node on the tailnet.

Signed-off-by: Benson Wong <benson@tailscale.com>
@mostlygeek mostlygeek force-pushed the mg/local-tailscaled-warn branch from ab13a81 to 3c2da93 Compare May 20, 2026 17:25
Copy link
Copy Markdown
Contributor

@lkosewsk lkosewsk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I consider myself warned

@mostlygeek mostlygeek merged commit a9340f0 into main May 21, 2026
2 checks passed
@mostlygeek mostlygeek deleted the mg/local-tailscaled-warn branch May 21, 2026 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants