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

ACL issue with username #1080

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

Originally created by @gianlucagiacometti on GitHub (Aug 7, 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

I have a couple of users:

root@headscale:~# headscale users list
ID | Name | Username | Email | Created
1  |      | john|       | 2025-06-25 14:36:43
2  |      | hannah   |       | 2025-08-06 22:01:26

When I set ACLs 'per user', I am forced to add an '@' after the username (i.e. john@), otherwise I cannot save the configuration.

    "acls": [
        {
            "#ha-meta": {
                "name": "PolicyForJack",
                "open": true
            },
            "action": "accept",
            "src": [
                "john@"
            ],
            "dst": [
                "*:*"
            ]
        },
...

The UI does not act as such, and it just inserts 'john'. This forces me to edit the config manually and correct the issue before saving.
I use headscale-admin, but I guess it's not an issue of the UI.

Expected Behavior

Either the UI should automatically add an '@' to the username, or usernames without '@' should be allowed.

Steps To Reproduce

  1. create a user
  2. create a policy with source the username
  3. save the configuration

Environment

- OS: Ubuntu 24.04
- Headscale version: 0.26.1
- Tailscale version: last, different OS

Runtime environment

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

Debug information

No issue with tailscale

Originally created by @gianlucagiacometti on GitHub (Aug 7, 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 I have a couple of users: ``` root@headscale:~# headscale users list ID | Name | Username | Email | Created 1 | | john| | 2025-06-25 14:36:43 2 | | hannah | | 2025-08-06 22:01:26 ``` When I set ACLs 'per user', I am forced to add an '@' after the username (i.e. john@), otherwise I cannot save the configuration. ``` "acls": [ { "#ha-meta": { "name": "PolicyForJack", "open": true }, "action": "accept", "src": [ "john@" ], "dst": [ "*:*" ] }, ... ``` The UI does not act as such, and it just inserts 'john'. This forces me to edit the config manually and correct the issue before saving. I use headscale-admin, but I guess it's not an issue of the UI. ### Expected Behavior Either the UI should automatically add an '@' to the username, or usernames without '@' should be allowed. ### Steps To Reproduce 1. create a user 2. create a policy with source the username 3. save the configuration ### Environment ```markdown - OS: Ubuntu 24.04 - Headscale version: 0.26.1 - Tailscale version: last, different OS ``` ### Runtime environment - [x] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Debug information No issue with tailscale
adam added the bug label 2025-12-29 02:28:09 +01:00
adam closed this issue 2025-12-29 02:28:09 +01:00
adam commented 2025-12-29 02:28:09 +01:00
Author
Owner
Copy Link

@nblock commented on GitHub (Aug 7, 2025):

This is an issue with the UI.

@nblock commented on GitHub (Aug 7, 2025): This is an issue with the UI.
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#1080
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?