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

[Bug] Headscale tags differ conceptually from Tailscale tags #914

New Issue
Closed
opened 2025-12-29 02:25:54 +01:00 by adam · 1 comment
adam commented 2025-12-29 02:25:54 +01:00
Owner
Copy Link

Originally created by @adnandaut on GitHub (Jan 21, 2025).

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The tagOwners section of my ACLs reads as follows:

  "tagOwners": {
    "tag:test": [ "group:admin" ],
  },

When trying to create an auth key with the headscale CLI for that tag, the operation fails, because it asks for a user account to tie the tag to:

$ headscale preauthkeys create --tags test
required flag(s) "user" not set

Expected Behavior

From the Tailscale documenation on auth keys

An auth key authenticates a device as the user who generated the key. […]
However, if you use tags with an auth key, a device that uses the auth key assumes the identity of the tags applied to it.

and on tags

Tags are essentially service accounts […]
Other key characteristics of tags include:

  • Applying a tag to a device removes any user-based authentication.
  • [...]
  • Tags are defined in the tailnet policy file in the tagOwners section.

I would expect to be able to create preauth keys that are tied to either a user or to tags , while I would expect an attempt to create a preauth key that is tied to a user and a tag at the same time to yield an error. In Tailscale, it does not appear to be possible to have a device be owned by a user and a tag at the same time.

Steps To Reproduce

I hope the steps for reproduction are relatively clear from the "Current behavior" section.

Environment

- OS: Docker
- Headscale version: 0.23.0
- Tailscale version: 1.78.1

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

No response

Originally created by @adnandaut on GitHub (Jan 21, 2025). ### Is this a support request? - [x] This is not a support request ### Is there an existing issue for this? - [x] I have searched the existing issues ### Current Behavior The tagOwners section of my ACLs reads as follows: ```json "tagOwners": { "tag:test": [ "group:admin" ], }, ``` When trying to create an auth key with the headscale CLI for that tag, the operation fails, because it asks for a user account to tie the tag to: ``` $ headscale preauthkeys create --tags test required flag(s) "user" not set ``` ### Expected Behavior From the Tailscale documenation [on auth keys](https://tailscale.com/kb/1085/auth-keys) > An auth key authenticates a device as the user who generated the key. […] > However, if you use [tags](https://tailscale.com/kb/1068/tags#best-practices) with an auth key, a device that uses the auth key assumes the identity of the tags applied to it. and [on tags](https://tailscale.com/kb/1068/tags) > Tags are essentially service accounts […] > Other key characteristics of tags include: > - Applying a tag to a device removes any user-based authentication. > - [...] > - Tags are defined in the tailnet policy file in the tagOwners section. I would expect to be able to create preauth keys that are tied to either a user or to tags , while I would expect an attempt to create a preauth key that is tied to a user and a tag at the same time to yield an error. In Tailscale, it does not appear to be possible to have a device be owned by a user and a tag at the same time. ### Steps To Reproduce I hope the steps for reproduction are relatively clear from the "Current behavior" section. ### Environment ```markdown - OS: Docker - Headscale version: 0.23.0 - Tailscale version: 1.78.1 ``` ### Runtime environment - [x] Headscale is behind a (reverse) proxy - [x] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:25:54 +01:00
adam closed this issue 2025-12-29 02:25:54 +01:00
adam commented 2025-12-29 02:25:54 +01:00
Author
Owner
Copy Link

@adnandaut commented on GitHub (Jan 21, 2025):

Sorry, I wasn't searching for "tag", just for "preauth".
This is a duplicate of #1369.

@adnandaut commented on GitHub (Jan 21, 2025): Sorry, I wasn't searching for "tag", just for "preauth". This is a duplicate of #1369.
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 bug
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#914
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?