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

Azure application device flow not supported #272

New Issue
Open
opened 2025-11-20 05:08:56 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 05:08:56 -05:00
Owner
Copy Link

Originally created by @mlsmaycon on GitHub (Feb 6, 2023).

Describe the problem
Our client doesn't support Azure application device flow. We need to add a check for a response without a complete URL. Besides that, we need to investigate the best option for scope request as our current OIDC flow only send openid and expected that the access token will match the correct audiance.

Options for us:

  • Send more scopes in the device request
  • Use ID token for validation and management login instead of access token (if no other option)

To Reproduce
Steps to reproduce the behavior:

  1. Configure a azure APP for authentication
  2. Configure Netbird with Azure information
  3. Attempt to login
  4. See error where client opens regular file explorer instead of browser
  5. Besides that, after login token is invalid

Expected behavior
Client authentication to work the same way as with auth0

Originally created by @mlsmaycon on GitHub (Feb 6, 2023). **Describe the problem** Our client doesn't support Azure application device flow. We need to add a check for a response without a complete URL. Besides that, we need to investigate the best option for scope request as our current OIDC flow only send openid and expected that the access token will match the correct audiance. Options for us: - Send more scopes in the device request - Use ID token for validation and management login instead of access token (if no other option) **To Reproduce** Steps to reproduce the behavior: 1. Configure a azure APP for authentication 2. Configure Netbird with Azure information 3. Attempt to login 4. See error where client opens regular file explorer instead of browser 5. Besides that, after login token is invalid **Expected behavior** Client authentication to work the same way as with auth0
saavagebueno added the bug label 2025-11-20 05:08:56 -05:00
saavagebueno commented 2025-11-20 05:08:57 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 17, 2025):

@mlsmaycon is it still pending a fix?

@nazarewk commented on GitHub (Apr 17, 2025): @mlsmaycon is it still pending a fix?
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 bug
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#272
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?