SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-16 13:12:11 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Feature: Reauthentication after disconnect #279

New Issue
Closed
opened 2025-11-20 05:09:01 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 05:09:01 -05:00
Owner
Copy Link

Originally created by @giezi on GitHub (Mar 2, 2023).

Is your feature request related to a problem? Please describe.
The feature request is related to improve the security.

Describe the solution you'd like
For security reasons, we want that when a user disconnects, he has to re-authenticate. It would be great if we could have a "setting" that could be set per user to control the disconnect behaviour.

Describe alternatives you've considered
None.

Originally created by @giezi on GitHub (Mar 2, 2023). **Is your feature request related to a problem? Please describe.** The feature request is related to improve the security. **Describe the solution you'd like** For security reasons, we want that when a user disconnects, he has to re-authenticate. It would be great if we could have a "setting" that could be set per user to control the disconnect behaviour. **Describe alternatives you've considered** None.
saavagebueno commented 2025-11-20 05:09:01 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 2, 2023):

Hello @giezi we are currently working on a time-based peer expiration, where peers activated by users will require authentication after N hours (from 1 hour to 180 days).

@mlsmaycon commented on GitHub (Mar 2, 2023): Hello @giezi we are currently working on a time-based peer expiration, where peers activated by users will require authentication after N hours (from 1 hour to 180 days).
saavagebueno commented 2025-11-20 05:09:02 -05:00
Author
Owner
Copy Link

@e-renna commented on GitHub (Mar 3, 2023):

Hello @giezi we are currently working on a time-based peer expiration, where peers activated by users will require authentication after N hours (from 1 hour to 180 days).

Would there be a setting to disable the expiration? e.g. for a peer that is used for a service (like a DNS server) rather than a user endpoint

@e-renna commented on GitHub (Mar 3, 2023): > Hello @giezi we are currently working on a time-based peer expiration, where peers activated by users will require authentication after N hours (from 1 hour to 180 days). Would there be a setting to disable the expiration? e.g. for a peer that is used for a service (like a DNS server) rather than a user endpoint
saavagebueno commented 2025-11-20 05:09:02 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 3, 2023):

@e-renna yes the feature will be enabled for new accounts. For existing accounts you can choose to enable in the account settings and you can also choose to disable expiration for specific peers.

@mlsmaycon commented on GitHub (Mar 3, 2023): @e-renna yes the feature will be enabled for new accounts. For existing accounts you can choose to enable in the account settings and you can also choose to disable expiration for specific peers.
saavagebueno commented 2025-11-20 05:09:02 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 3, 2023):

See https://github.com/netbirdio/netbird/releases/tag/v0.14.2

@mlsmaycon commented on GitHub (Mar 3, 2023): See https://github.com/netbirdio/netbird/releases/tag/v0.14.2
saavagebueno commented 2025-11-20 05:09:02 -05:00
Author
Owner
Copy Link

@giezi commented on GitHub (Mar 3, 2023):

@mlsmaycon Absolutely amazing!!! Many thanks!!!

@giezi commented on GitHub (Mar 3, 2023): @mlsmaycon Absolutely amazing!!! Many thanks!!!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#279
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?