Has anyone managed to get these three services working properly together? I’m having trouble with the authentication flow. When I log into PocketID successfully, everything seems fine at first. But then when it tries to redirect me back to the Netbird dashboard at https://netbird.mydomain.com/peers, the page just sits there with a loading spinner that never finishes. I’ve checked the logs but can’t figure out what’s causing the hang. The authentication appears to complete on the PocketID side, but something breaks during the handoff back to Netbird. Any ideas what might be going wrong with this setup?
Had the same issue a few months ago with a different SSO provider. That spinning loader usually means CORS problems or JWT token validation is failing. Check your Netbird management server logs - not the dashboard ones. My token was passing through fine, but the management server couldn’t verify it against PocketID’s public key. Double-check that your Netbird config has the right PocketID issuer URL and both services can actually talk to each other. Also make sure PocketID’s returning the claims Netbird needs for user ID.
yup, sounds like a redirect uri mismatch. double check that the PocketID callback url matches what netbird needs. also, clearing your cache and cookies can help – they often mess with auth flows!
That infinite spinner after PocketID auth usually means there’s a session issue between the services. I had this exact problem when my Netbird wasn’t set up right for OAuth2 completion. Check that your Netbird management service is running on the right port and your browser can reach it - sometimes the dashboard loads fine but can’t talk to the backend API during auth. Also make sure the PocketID token has the right permissions and includes all the user metadata fields it needs. For me, the fix was making sure Netbird could properly validate the OAuth2 state parameter that comes back from PocketID.