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] Version 0.27.0 when using oidc doesn't respect expiry parameter on session lengths #1136

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

Originally created by @aalmenar on GitHub (Nov 4, 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

Using version 0.26.1, when you set an expiry time in oidc, it disconnects clients after time has passed but since update to version 0.27.0, expiration is set correctly: 2025-11-07 14:49:24 but after som time running, its set to 0001-01-01 00:00:00

Expected Behavior

To keep the expiration time untouched.

Steps To Reproduce

Use headscale with oidc:

oidc:
    expiry: 72h
    use_expiry_from_token: false

Environment

- OS: Debian 12
- Headscale version: 0.27.0
- Tailscale version: 1.80 to 1.90.6 (Tested)

Runtime environment

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

Debug information

...

Originally created by @aalmenar on GitHub (Nov 4, 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 Using version 0.26.1, when you set an expiry time in oidc, it disconnects clients after time has passed but since update to version 0.27.0, expiration is set correctly: 2025-11-07 14:49:24 but after som time running, its set to 0001-01-01 00:00:00 ### Expected Behavior To keep the expiration time untouched. ### Steps To Reproduce Use headscale with oidc: ```yaml oidc: expiry: 72h use_expiry_from_token: false ``` ### Environment ```markdown - OS: Debian 12 - Headscale version: 0.27.0 - Tailscale version: 1.80 to 1.90.6 (Tested) ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Debug information ...
adam added the bugregression labels 2025-12-29 02:28:29 +01:00
adam closed this issue 2025-12-29 02:28:30 +01:00
adam commented 2025-12-29 02:28:30 +01:00
Author
Owner
Copy Link

@nblock commented on GitHub (Nov 5, 2025):

Confirmed, the expiration is correctly set (2025-11-08 20:15:30) on initial authentication but is reset to 0001-01-01 00:00:00 when tailscaled is restarted on the node.

@nblock commented on GitHub (Nov 5, 2025): Confirmed, the expiration is correctly set (`2025-11-08 20:15:30`) on initial authentication but is reset to ` 0001-01-01 00:00:00` when tailscaled is restarted on the node.
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 regression
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#1136
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?