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

NetBird's Azure Enterprise App client secret looks to have expired. (Error happening on multiple of our clients now). #2363

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

Originally created by @kmhadmin on GitHub (Oct 10, 2025).

Describe the problem

We had one client today Oct 10th Approx. 4:48pm PST send in a support ticket stating that all users were getting any error when trying to connect via Netbird.

This client currnetly is setup to Authenticate via their M365 accounts and when any attempt was made to login this way. The user would recieve any error message.

There was an error logging you in.
Error: AADSTS7000222: The provided client secret keys for app '7a7538de-b7ed-4e49-befe-edbe74d5e0a1' are expired.

We tested it on our internal Netbird account which also is setup to authenticate via our M365 accounts and all worked normal at that moment. So we believed it was the IDP Sync api to Entra ID client secret that expired but when we check that. It was still good till 10/2027.

Then we got another support request from another client stating the exact same issue and then two more shortly after that. Then finally our own internal Netbird started to suffer the same problem.

Looking at error a little closer now, we relized that App ID in the error was the same for all clients and pointed to the Netbird Enterprise App ID that is created the first time when Entra ID Global Admin for the tenant authorizes the SSO ability. Now all clients that use M365 authentication for their Netbird accounts are all recieving the same error and are unable to loggin at all. Realizing that this app is actually published by Netbird. We are now reaching out so you guys can to check your published Enterprise App on Azure to see what is going on.

To Reproduce

We can reproduce this by simply going to the Netbird website or attempting to connect to the Netbird via VPN client. Once you reach the login page, and select continue with Microsoft. It appears to authenticate and then just right when it looks like it is going through. You are presented with the error message.

Full Error message being preseted on all clients tenants.

"There was an error logging you in.
Error: AADSTS7000222: The provided client secret keys for app '7a7538de-b7ed-4e49-befe-edbe74d5e0a1' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds. Trace ID: 501bddad-eaf4-483f-baf2-7bdda7a14a00 Correlation ID: 93d8b879-e1ac-4f7c-9e81-4a5a389ee2bc Timestamp: 2025-10-11 01:29:11Z"

Note: This is only affecting clients the use M365/Entra ID to authenticate to Netbird. Our clients that under Google Workspace for authentication to Netbird do not seem to be affected.

Expected behavior

Expected to login/authenticate the users Netbird account.

Are you using NetBird Cloud?

Yes all clients are using NetBird Cloud

NetBird version

V59.5

Is any other VPN software installed?

No

Debug output

There was an error logging you in.
Error: AADSTS7000222: The provided client secret keys for app '7a7538de-b7ed-4e49-befe-edbe74d5e0a1' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds. Trace ID: 501bddad-eaf4-483f-baf2-7bdda7a14a00 Correlation ID: 93d8b879-e1ac-4f7c-9e81-4a5a389ee2bc Timestamp: 2025-10-11 01:29:11Z

Note, Client side Entra ID shows no login error in any of the tenants sign audits and when searching for Correlation ID: 93d8b879-e1ac-4f7c-9e81-4a5a389ee2bc. Nothing is found.

Screenshots

Image

Additional context

Add any other context about the problem here.

We have already attempted to delete the Enterprise App on two client tenants as well as our own. Waited an hour and then went through the re-autherization process to recreate the Netbird Enterprise App and right at the end it completes then you are presented with the same error message.

We are able to log into each clients Netbird tenant with our admin accounts via username and password we made when each of their NetBird accounts were created but doesn't do our clients much good.

Originally created by @kmhadmin on GitHub (Oct 10, 2025). **Describe the problem** We had one client today Oct 10th Approx. 4:48pm PST send in a support ticket stating that all users were getting any error when trying to connect via Netbird. This client currnetly is setup to Authenticate via their M365 accounts and when any attempt was made to login this way. The user would recieve any error message. There was an error logging you in. Error: AADSTS7000222: The provided client secret keys for app '7a7538de-b7ed-4e49-befe-edbe74d5e0a1' are expired. We tested it on our internal Netbird account which also is setup to authenticate via our M365 accounts and all worked normal at that moment. So we believed it was the IDP Sync api to Entra ID client secret that expired but when we check that. It was still good till 10/2027. Then we got another support request from another client stating the exact same issue and then two more shortly after that. Then finally our own internal Netbird started to suffer the same problem. Looking at error a little closer now, we relized that App ID in the error was the same for all clients and pointed to the Netbird Enterprise App ID that is created the first time when Entra ID Global Admin for the tenant authorizes the SSO ability. Now all clients that use M365 authentication for their Netbird accounts are all recieving the same error and are unable to loggin at all. Realizing that this app is actually published by Netbird. We are now reaching out so you guys can to check your published Enterprise App on Azure to see what is going on. **To Reproduce** We can reproduce this by simply going to the Netbird website or attempting to connect to the Netbird via VPN client. Once you reach the login page, and select continue with Microsoft. It appears to authenticate and then just right when it looks like it is going through. You are presented with the error message. Full Error message being preseted on all clients tenants. "There was an error logging you in. Error: AADSTS7000222: The provided client secret keys for app '7a7538de-b7ed-4e49-befe-edbe74d5e0a1' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds. Trace ID: 501bddad-eaf4-483f-baf2-7bdda7a14a00 Correlation ID: 93d8b879-e1ac-4f7c-9e81-4a5a389ee2bc Timestamp: 2025-10-11 01:29:11Z" Note: This is only affecting clients the use M365/Entra ID to authenticate to Netbird. Our clients that under Google Workspace for authentication to Netbird do not seem to be affected. **Expected behavior** Expected to login/authenticate the users Netbird account. **Are you using NetBird Cloud?** Yes all clients are using NetBird Cloud **NetBird version** V59.5 **Is any other VPN software installed?** No **Debug output** There was an error logging you in. Error: AADSTS7000222: The provided client secret keys for app '7a7538de-b7ed-4e49-befe-edbe74d5e0a1' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds. Trace ID: 501bddad-eaf4-483f-baf2-7bdda7a14a00 Correlation ID: 93d8b879-e1ac-4f7c-9e81-4a5a389ee2bc Timestamp: 2025-10-11 01:29:11Z Note, Client side Entra ID shows no login error in any of the tenants sign audits and when searching for Correlation ID: 93d8b879-e1ac-4f7c-9e81-4a5a389ee2bc. Nothing is found. **Screenshots** <img width="1929" height="1041" alt="Image" src="https://github.com/user-attachments/assets/ad82d951-0b9c-4318-9d07-da3b7ca197cb" /> **Additional context** Add any other context about the problem here. We have already attempted to delete the Enterprise App on two client tenants as well as our own. Waited an hour and then went through the re-autherization process to recreate the Netbird Enterprise App and right at the end it completes then you are presented with the same error message. We are able to log into each clients Netbird tenant with our admin accounts via username and password we made when each of their NetBird accounts were created but doesn't do our clients much good.
saavagebueno added the triage-needed label 2025-11-20 07:08:36 -05:00
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 triage-needed
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#2363
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?