Allow OIDC tokens for API request #493

Closed
opened 2025-12-29 02:19:05 +01:00 by adam · 3 comments
Owner

Originally created by @acul009 on GitHub (May 1, 2023).

Feature request

I would like to use OIDC tokens to manage some aspects of my machine. This includes adding tags to a machine.
When using an ID token, there would already be basic code to identify the user, which could be a bit expanded to be used by the api.

This could increase security for external managment UIs, as the Interface would no longer need to use an "administrative" token. Current Interfaces have to handle Access Control seperately again and have to protect their Headscale token.
When allowing OIDC ID-Tokens, the ui would only need to obtain such a token and then use is to e.g. query machines, which would only return the machines this user is allowed to see or edit.

Originally created by @acul009 on GitHub (May 1, 2023). **Feature request** I would like to use OIDC tokens to manage some aspects of my machine. This includes adding tags to a machine. When using an ID token, there would already be basic code to identify the user, which could be a bit expanded to be used by the api. This could increase security for external managment UIs, as the Interface would no longer need to use an "administrative" token. Current Interfaces have to handle Access Control seperately again and have to protect their Headscale token. When allowing OIDC ID-Tokens, the ui would only need to obtain such a token and then use is to e.g. query machines, which would only return the machines this user is allowed to see or edit.
adam added the enhancementstale labels 2025-12-29 02:19:05 +01:00
adam closed this issue 2025-12-29 02:19:05 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 28, 2023):

This issue is stale because it has been open for 180 days with no activity.

@github-actions[bot] commented on GitHub (Oct 28, 2023): This issue is stale because it has been open for 180 days with no activity.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 11, 2023):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Nov 11, 2023): This issue was closed because it has been inactive for 14 days since being marked as stale.
Author
Owner

@korfuri commented on GitHub (Nov 15, 2023):

I'd like to reopen this. I'm running headscale and not being able to integrate with my OIDC SSO is a pain: I have to manage headscale tokens out of band, which in practice means sshing to a machine and generating a token via the CLI.

Being able to rely on OIDC tokens would abstract all of this.

@korfuri commented on GitHub (Nov 15, 2023): I'd like to reopen this. I'm running headscale and not being able to integrate with my OIDC SSO is a pain: I have to manage headscale tokens out of band, which in practice means sshing to a machine and generating a token via the CLI. Being able to rely on OIDC tokens would abstract all of this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#493