starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Feature] Pre-auth keys without user binding & group tagged devices #895

New Issue
Closed
opened 2025-12-29 02:25:33 +01:00 by adam · 4 comments
adam commented 2025-12-29 02:25:33 +01:00
Owner
Copy Link

Originally created by @alirezamirsepassi on GitHub (Jan 5, 2025).

Use case

It would be super helpful if we could create pre-auth keys without having to bind them to a specific user. This would make the setup process a lot more flexible and align with how Tailscale does it. Sometimes, you just want to provision devices without worrying about assigning them to users upfront.

Also, in the interface, it’d be awesome to have all tagged devices grouped under a "Tagged Devices" section. This would make things much cleaner and easier to navigate, especially when you’re managing a lot of nodes. It just feels like a natural way to organize them.

Description

  1. Pre-auth keys without user binding: Add a way to generate pre-auth keys that don’t require a user assignment. This gives more freedom when onboarding devices, especially for shared or temporary setups.

  2. Group tagged devices: Update the interface to show a dedicated "Tagged Devices" section. It’s a small change, but it would make finding and managing tagged devices so much simpler.

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

  • For pre-auth keys: Update the backend logic and the database schema so keys can be created without linking them to a user.

  • For grouping tagged devices: In the function that returns the user profile, check if the node is tagged; if so, use "Tagged Devices" as DisplayName

Originally created by @alirezamirsepassi on GitHub (Jan 5, 2025). ### Use case It would be super helpful if we could create pre-auth keys without having to bind them to a specific user. This would make the setup process a lot more flexible and align with how Tailscale does it. Sometimes, you just want to provision devices without worrying about assigning them to users upfront. Also, in the interface, it’d be awesome to have all tagged devices grouped under a "Tagged Devices" section. This would make things much cleaner and easier to navigate, especially when you’re managing a lot of nodes. It just feels like a natural way to organize them. ### Description 1. **Pre-auth keys without user binding**: Add a way to generate pre-auth keys that don’t require a user assignment. This gives more freedom when onboarding devices, especially for shared or temporary setups. 2. **Group tagged devices**: Update the interface to show a dedicated "Tagged Devices" section. It’s a small change, but it would make finding and managing tagged devices so much simpler. ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? - For pre-auth keys: Update the backend logic and the database schema so keys can be created without linking them to a user. - For grouping tagged devices: In the function that returns the user profile, check if the node is tagged; if so, use "Tagged Devices" as DisplayName
adam added the enhancementno-stale-botpolicy 📝tags labels 2025-12-29 02:25:33 +01:00
adam closed this issue 2025-12-29 02:25:33 +01:00
adam commented 2025-12-29 02:25:33 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Jan 6, 2025):

Sounds related/overlapping to #1369

@kradalby commented on GitHub (Jan 6, 2025): Sounds related/overlapping to #1369
adam commented 2025-12-29 02:25:34 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (May 7, 2025):

While tags has not been focused on in this release, it might have been touched up and I would be grateful to hear feedback if the current beta changed anything for this issue.

@kradalby commented on GitHub (May 7, 2025): While tags has not been focused on in this release, it might have been touched up and I would be grateful to hear feedback if the current beta changed anything for this issue.
adam commented 2025-12-29 02:25:34 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (May 16, 2025):

Pre-auth keys without user binding: Add a way to generate pre-auth keys that don’t require a user assignment. This gives more freedom when onboarding devices, especially for shared or temporary setups.

We will make it so when you create a pre auth key it is either attached to a user (if no tags are given) or a tag. When a device is tagged, it will not be associated with a user.

@kradalby commented on GitHub (May 16, 2025): > Pre-auth keys without user binding: Add a way to generate pre-auth keys that don’t require a user assignment. This gives more freedom when onboarding devices, especially for shared or temporary setups. We will make it so when you create a pre auth key it is _either_ attached to a user (if no tags are given) or a tag. When a device is tagged, it will not be associated with a user.
adam commented 2025-12-29 02:25:34 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Dec 11, 2025):

Changes to separate the tags from users has been merged into main in #2885 and #2931. I will encourage you to help testing this if you are able to build main and run it.

I will close this to track progress, but there might still be bugs and the likes related to this change. As part of hardening this feature, we are tracking all related tags bugs over time in v0.28.0 milestone.

@kradalby commented on GitHub (Dec 11, 2025): Changes to separate the tags from users has been merged into `main` in #2885 and #2931. I will encourage you to help testing this if you are able to build `main` and run it. I will close this to track progress, but there might still be bugs and the likes related to this change. As part of hardening this feature, we are tracking all related tags bugs over time in [v0.28.0 milestone](https://github.com/juanfont/headscale/milestone/13).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label enhancement no-stale-bot policy 📝 tags
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#895
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?