SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-10 09:22:09 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Error for idp token expire even if IdpSignKeyRefreshEnabled enabled #543

New Issue
Open
opened 2025-11-20 05:13:27 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:13:27 -05:00
Owner
Copy Link

Originally created by @Fantu on GitHub (Dec 12, 2023).

Hi, I have netbird selfhosted that use idp google, initially after some days always make impossible login until reboot.
After found "IdpSignKeyRefreshEnabled" I enabled it and for long time I not had issue.
Today same issue appaired (at least seems), here latest logs before reboot (after reboot return to work correctly):

infrastructure_files-management-1  | 2023-12-12T09:12:27Z ERRO management/server/http/util/util.go:80: got a handler error: token invalid
infrastructure_files-management-1  | 2023-12-12T09:12:27Z ERRO management/server/telemetry/http_api_metrics.go:181: HTTP response 4056351373: GET /api/users status 401
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/jwtclaims/jwtValidator.go:158: error parsing token: unable to find appropriate key
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/http/middleware/auth_middleware.go:65: Error when validating JWT claims: Error parsing token: unable to find appropriate key
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/http/util/util.go:80: got a handler error: token invalid
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/telemetry/http_api_metrics.go:181: HTTP response 1058967340: GET /api/users status 401
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/jwtclaims/jwtValidator.go:158: error parsing token: unable to find appropriate key
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/http/middleware/auth_middleware.go:65: Error when validating JWT claims: Error parsing token: unable to find appropriate key
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/http/util/util.go:80: got a handler error: token invalid
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/telemetry/http_api_metrics.go:181: HTTP response 3694887989: GET /api/users status 401
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/jwtclaims/jwtValidator.go:158: error parsing token: unable to find appropriate key
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/http/middleware/auth_middleware.go:65: Error when validating JWT claims: Error parsing token: unable to find appropriate key
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/http/util/util.go:80: got a handler error: token invalid
infrastructure_files-management-1  | 2023-12-12T09:12:28Z ERRO management/server/telemetry/http_api_metrics.go:181: HTTP response 3769408553: GET /api/groups status 401

I couldn't keep it not working for more in-depth debugging because we needed to use it, let me know if there is any more data I can provide even if the problem is no longer occurring.

Originally created by @Fantu on GitHub (Dec 12, 2023). Hi, I have netbird selfhosted that use idp google, initially after some days always make impossible login until reboot. After found "IdpSignKeyRefreshEnabled" I enabled it and for long time I not had issue. Today same issue appaired (at least seems), here latest logs before reboot (after reboot return to work correctly): ``` infrastructure_files-management-1 | 2023-12-12T09:12:27Z ERRO management/server/http/util/util.go:80: got a handler error: token invalid infrastructure_files-management-1 | 2023-12-12T09:12:27Z ERRO management/server/telemetry/http_api_metrics.go:181: HTTP response 4056351373: GET /api/users status 401 infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/jwtclaims/jwtValidator.go:158: error parsing token: unable to find appropriate key infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/http/middleware/auth_middleware.go:65: Error when validating JWT claims: Error parsing token: unable to find appropriate key infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/http/util/util.go:80: got a handler error: token invalid infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/telemetry/http_api_metrics.go:181: HTTP response 1058967340: GET /api/users status 401 infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/jwtclaims/jwtValidator.go:158: error parsing token: unable to find appropriate key infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/http/middleware/auth_middleware.go:65: Error when validating JWT claims: Error parsing token: unable to find appropriate key infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/http/util/util.go:80: got a handler error: token invalid infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/telemetry/http_api_metrics.go:181: HTTP response 3694887989: GET /api/users status 401 infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/jwtclaims/jwtValidator.go:158: error parsing token: unable to find appropriate key infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/http/middleware/auth_middleware.go:65: Error when validating JWT claims: Error parsing token: unable to find appropriate key infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/http/util/util.go:80: got a handler error: token invalid infrastructure_files-management-1 | 2023-12-12T09:12:28Z ERRO management/server/telemetry/http_api_metrics.go:181: HTTP response 3769408553: GET /api/groups status 401 ``` I couldn't keep it not working for more in-depth debugging because we needed to use it, let me know if there is any more data I can provide even if the problem is no longer occurring.
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#543
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?