Skip to content

Support device code login for account and unified hosts - #7710

Merged
maksim-zuev-db merged 12 commits into
mainfrom
device-code-account-hosts
Nov 18, 2026
Merged

maksim-zuev-db merged 12 commits into
mainfrom
device-code-account-hosts

Conversation

@maksim-zuev-db

@maksim-zuev-db maksim-zuev-db commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Changes

  • Remove the checks that limited auth login --use-device-code to workspace hosts: account and unified (SPOG) hosts are no longer rejected, --skip-workspace can be combined with --use-device-code, and the profile picker lists account profiles again. setHostAndAccountId is merged back into one function, since it was only split to fit the host check in.
  • Classic account hosts build their OAuth endpoints without fetching the OIDC discovery document, so device code login now fetches /oidc/accounts/<account-id>/.well-known/oauth-authorization-server to find device_authorization_endpoint. Unified hosts already fetch it.
  • The second step of the non-interactive login now also checks the account ID, like the host. The token endpoint of account and unified hosts depends on the account ID, so a login started for one account would otherwise send its device code to another account's token endpoint.
  • device code login is not enabled for this workspace becomes ... for this host, and --use-device-code requires a workspace host becomes ... requires a host.
  • Update docs/device-code-login.md and cmd/auth/README.md.

Why

The server now supports device code login for account and unified hosts. It is opt-in per account, and so far only in dev and staging.

Tests

  • Unit tests for account and unified hosts, with and without the advertised endpoint.
  • The fake server in libs/testserver serves account-scoped OIDC routes. A new device-code/unified-host acceptance test covers an account-level and a workspace-level login on a unified host, and checks that a login started for one account cannot be completed for another. unsupported-host covers an account without device code login.
  • Manually tested on dev accounts and SPOG hosts: account-level and workspace-level logins on a unified host, and accounts without device code login enabled.

This pull request and its description were written by Isaac.

Device code login is now enabled on the server for account and unified
(SPOG) hosts, so remove the checks that limited it to workspace hosts.
Classic account hosts build their OAuth endpoints without fetching the
OIDC discovery document, so device code login fetches it to find the
device authorization endpoint.

Co-authored-by: Isaac <no-reply@databricks.com>
@github-actions github-actions Bot added the auth label Nov 17, 2026
@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Commit: 7bde7ae2f | Workflow run

Regression test report

Selected 4 changed tests (limit=20, 0 not selected)

4 tests: regression=3 unreleased=0 coverage=1 failing=0
test branch main (9175b8f) latest (v1.26.0)
TestAccept/cmd/auth/login/device-code/non-interactive/errors ✅ ❌ ❌
TestAccept/cmd/auth/login/device-code/precondition ✅ ✅ ✅
TestAccept/cmd/auth/login/device-code/unified-host ✅ ❌ ❌
TestAccept/cmd/auth/login/device-code/unsupported-host ✅ ❌ ❌
TestAccept/cmd/auth/login/device-code/non-interactive/errors: branch ✅ | main (9175b8f) ❌ | latest (v1.26.0) ❌

main (9175b8f):

acceptance_test.go:1384: Diff:
        --- cmd/auth/login/device-code/non-interactive/errors/output.txt
        +++ /tmp/TestAcceptcmdauthlogindevice-codenon-interactiveerrors2587937864/002/output.txt
        @@ -15,10 +15,10 @@
         === Missing host
         
         >>> musterr [CLI] auth login --use-device-code
        -Error: --use-device-code requires a host. Pass it as an argument or with --host
        +Error: --use-device-code requires a workspace host. Pass it as an argument or with --host
         
         >>> musterr [CLI] auth login --profile test --use-device-code --user-code WDJB-0001 --confirmation-code FTFA-QQKY
        -Error: --use-device-code requires a host. Pass it as an argument or with --host
        +Error: --use-device-code requires a workspace host. Pass it as an argument or with --host
         
         === Incomplete flags of the second step
         
        @@ -40,7 +38,7 @@
         
         >>> musterr [CLI] auth login --host https://accounts.cloud.databricks.test --use-device-code --user-code WDJB-0001 --confirmation-code FTFA-QQKY
         Warn: [hostmetadata] failed to fetch host metadata for https://accounts.cloud.databricks.test, will skip for 1m0s
        -Error: the command is being run in a non-interactive environment, please specify an account ID using --account-id
        +Error: --use-device-code is only supported for workspace hosts
         
         === Profile scoped to resources
         
        
    acceptance_test.go:1162: 
        LOG.expired: Using a browser on another device, visit:
        LOG.expired: http://127.0.0.1:42345/device/verification
        LOG.expired: 
        LOG.expired: And enter the code:
        LOG.expired: WDJB-0002
        LOG.expired: 
        LOG.expired: Once finished, complete the login by running the same command with
        LOG.expired: --user-code WDJB-0002 and --confirmation-code set to the confirmation code
        LOG.expired: provided in your browser.
    acceptance_test.go:1162: 
        LOG.scopes: Using a browser on another device, visit:
        LOG.scopes: http://127.0.0.1:42345/device/verification
        LOG.scopes: 
        LOG.scopes: And enter the code:
        LOG.scopes: WDJB-0003
        LOG.scopes: 
        LOG.scopes: Once finished, complete the login by running the same command with
        LOG.scopes: --user-code WDJB-0003 and --confirmation-code set to the confirmation code
        LOG.scopes: provided in your browser.
    acceptance_test.go:1162: 
        LOG.wrong-code: Using a browser on another device, visit:
        LOG.wrong-code: http://127.0.0.1:42345/device/verification
        LOG.wrong-code: 
        LOG.wrong-code: And enter the code:
        LOG.wrong-code: WDJB-0001
        LOG.wrong-code: 
        LOG.wrong-code: Once finished, complete the login by running the same command with
        LOG.wrong-code: --user-code WDJB-0001 and --confirmation-code set to the confirmation code
        LOG.wrong-code: provided in your browser.
FAIL

latest (v1.26.0):

acceptance_test.go:1384: Diff:
        --- cmd/auth/login/device-code/non-interactive/errors/output.txt
        +++ /tmp/TestAcceptcmdauthlogindevice-codenon-interactiveerrors543760315/002/output.txt
        @@ -15,10 +15,10 @@
         === Missing host
         
         >>> musterr [CLI] auth login --use-device-code
        -Error: --use-device-code requires a host. Pass it as an argument or with --host
        +Error: --use-device-code requires a workspace host. Pass it as an argument or with --host
         
         >>> musterr [CLI] auth login --profile test --use-device-code --user-code WDJB-0001 --confirmation-code FTFA-QQKY
        -Error: --use-device-code requires a host. Pass it as an argument or with --host
        +Error: --use-device-code requires a workspace host. Pass it as an argument or with --host
         
         === Incomplete flags of the second step
         
        @@ -40,7 +38,7 @@
         
         >>> musterr [CLI] auth login --host https://accounts.cloud.databricks.test --use-device-code --user-code WDJB-0001 --confirmation-code FTFA-QQKY
         Warn: [hostmetadata] failed to fetch host metadata for https://accounts.cloud.databricks.test, will skip for 1m0s
        -Error: the command is being run in a non-interactive environment, please specify an account ID using --account-id
        +Error: --use-device-code is only supported for workspace hosts
         
         === Profile scoped to resources
         
        
    acceptance_test.go:1162: 
        LOG.expired: Using a browser on another device, visit:
        LOG.expired: http://127.0.0.1:37769/device/verification
        LOG.expired: 
        LOG.expired: And enter the code:
        LOG.expired: WDJB-0002
        LOG.expired: 
        LOG.expired: Once finished, complete the login by running the same command with
        LOG.expired: --user-code WDJB-0002 and --confirmation-code set to the confirmation code
        LOG.expired: provided in your browser.
    acceptance_test.go:1162: 
        LOG.scopes: Using a browser on another device, visit:
        LOG.scopes: http://127.0.0.1:37769/device/verification
        LOG.scopes: 
        LOG.scopes: And enter the code:
        LOG.scopes: WDJB-0003
        LOG.scopes: 
        LOG.scopes: Once finished, complete the login by running the same command with
        LOG.scopes: --user-code WDJB-0003 and --confirmation-code set to the confirmation code
        LOG.scopes: provided in your browser.
    acceptance_test.go:1162: 
        LOG.wrong-code: Using a browser on another device, visit:
        LOG.wrong-code: http://127.0.0.1:37769/device/verification
        LOG.wrong-code: 
        LOG.wrong-code: And enter the code:
        LOG.wrong-code: WDJB-0001
        LOG.wrong-code: 
        LOG.wrong-code: Once finished, complete the login by running the same command with
        LOG.wrong-code: --user-code WDJB-0001 and --confirmation-code set to the confirmation code
        LOG.wrong-code: provided in your browser.
FAIL
TestAccept/cmd/auth/login/device-code/unified-host: branch ✅ | main (9175b8f) ❌ | latest (v1.26.0) ❌

main (9175b8f):

acceptance_test.go:1384: Diff:
        --- cmd/auth/login/device-code/unified-host/output.txt
        +++ /tmp/TestAcceptcmdauthlogindevice-codeunified-host3099972103/002/output.txt
        @@ -2,49 +2,6 @@
         === Log in to the account
         
         >>> [CLI] auth login --host [DATABRICKS_URL]?a=spog-acct-123 --profile account --use-device-code
        -Using a browser on another device, visit:
        -[DATABRICKS_URL]/device/verification
        +Error: --use-device-code is only supported for workspace hosts
         
        -And enter the code:
        -WDJB-0001
        -
        -Once finished, complete the login by running the same command with
        ---user-code WDJB-0001 and --confirmation-code set to the confirmation code
        -provided in your browser.
        -
        ->>> musterr [CLI] auth login --host [DATABRICKS_URL]?a=other-acct --profile account --use-device-code --user-code WDJB-0001 --confirmation-code FTFA-QQKY
        -Error: the login for profile account was started with a different account ID. Complete it with the same command that started it. Run the same command without --user-code and --confirmation-code to start a new login
        -
        ->>> [CLI] auth login --host [DATABRICKS_URL]?a=spog-acct-123 --profile account --use-device-code --user-code WDJB-0001 --confirmation-code FTFA-QQKY
        -To use workspace commands, set workspace_id in your profile or pass --workspace-id.
        -Profile account was successfully saved
        -
        ->>> [CLI] auth token --profile account
        -json.access_token = "oauth-token";
        -
        -=== Log in to a workspace of the account
        -
        ->>> [CLI] auth login --host [DATABRICKS_URL]?a=spog-acct-123&o=12345 --profile workspace --use-device-code
        -Using a browser on another device, visit:
        -[DATABRICKS_URL]/device/verification
        -
        -And enter the code:
        -WDJB-0002
        -
        -Once finished, complete the login by running the same command with
        ---user-code WDJB-0002 and --confirmation-code set to the confirmation code
        -provided in your browser.
        -
        ->>> [CLI] auth login --host [DATABRICKS_URL]?a=spog-acct-123&o=12345 --profile workspace --use-device-code --user-code WDJB-0002 --confirmation-code FTFA-QQKY
        -Profile workspace was successfully saved
        -
        ->>> [CLI] auth token --profile workspace
        -json.access_token = "oauth-token";
        -
        -=== Device code requests
        -
        ->>> print_requests.py --oneline //oidc
        -{"method": "POST", "path": "/oidc/accounts/spog-acct-123/v1/device/auth", "raw_body": "client_id=databricks-cli&scope=offline_access+all-apis"}
        -{"method": "POST", "path": "/oidc/accounts/spog-acct-123/v1/token", "raw_body": "client_id=databricks-cli&confirmation_code=FTFAQQKY&device_code=device-code-1&grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Adevice_code"}
        -{"method": "POST", "path": "/oidc/accounts/spog-acct-123/v1/device/auth", "raw_body": "client_id=databricks-cli&scope=offline_access+all-apis"}
        -{"method": "POST", "path": "/oidc/accounts/spog-acct-123/v1/token", "raw_body": "client_id=databricks-cli&confirmation_code=FTFAQQKY&device_code=device-code-2&grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Adevice_code"}
        +Exit code: 1
        
    acceptance_test.go:1355: Missing output file: out.databrickscfg

latest (v1.26.0): same output as main (9175b8f)

TestAccept/cmd/auth/login/device-code/unsupported-host: branch ✅ | main (9175b8f) ❌ | latest (v1.26.0) ❌

main (9175b8f):

acceptance_test.go:1384: 
        	Error Trace:	/home/runner/work/cli/cli/libs/testdiff/testdiff.go:22
        	            				/home/runner/work/cli/cli/acceptance/acceptance_test.go:1384
        	            				/home/runner/work/cli/cli/acceptance/acceptance_test.go:1125
        	            				/home/runner/work/cli/cli/acceptance/acceptance_test.go:670
        	Error:      	Not equal: 
        	            	expected: "\n=== No host\n\n>>> musterr [CLI] auth login --profile new-profile --use-device-code\nError: --use-device-code requires a host. Pass it as an argument or with --host\n\n=== Workspace without device code login\n\n>>> musterr [CLI] auth login --host [DATABRICKS_URL] --profile test --use-device-code\nError: device code login is not enabled for this host\n\n>>> musterr [CLI] auth login --profile workspace --use-device-code\nError: device code login is not enabled for this host\n\n=== Account without device code login\n\n>>> DATABRICKS_DISCOVERY_URL=[DATABRICKS_URL]/oidc/accounts/spog-acct-123/.well-known/oauth-authorization-server musterr [CLI] auth login --host [DATABRICKS_URL]?a=spog-acct-123 --profile test --use-device-code\nError: device code login is not enabled for this host\n\n=== Device authorization requests\n\n>>> print_requests.py //device/auth\n"
        	            	actual  : "\n=== No host\n\n>>> musterr [CLI] auth login --profile new-profile --use-device-code\nError: --use-device-code requires a workspace host. Pass it as an argument or with --host\n\n=== Workspace without device code login\n\n>>> musterr [CLI] auth login --host [DATABRICKS_URL] --profile test --use-device-code\nError: device code login is not enabled for this workspace\n\n>>> musterr [CLI] auth login --profile workspace --use-device-code\nError: device code login is not enabled for this workspace\n\n=== Account without device code login\n\n>>> DATABRICKS_DISCOVERY_URL=[DATABRICKS_URL]/oidc/accounts/spog-acct-123/.well-known/oauth-authorization-server musterr [CLI] auth login --host [DATABRICKS_URL]?a=spog-acct-123 --profile test --use-device-code\nError: --use-device-code is only supported for workspace hosts\n\n=== Device authorization requests\n\n>>> print_requests.py //device/auth\n"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -4,3 +4,3 @@
        	            	 >>> musterr [CLI] auth login --profile new-profile --use-device-code
        	            	-Error: --use-device-code requires a host. Pass it as an argument or with --host
        	            	+Error: --use-device-code requires a workspace host. Pass it as an argument or with --host
        	            	 
        	            	@@ -9,6 +9,6 @@
        	            	 >>> musterr [CLI] auth login --host [DATABRICKS_URL] --profile test --use-device-code
        	            	-Error: device code login is not enabled for this host
        	            	+Error: device code login is not enabled for this workspace
        	            	 
        	            	 >>> musterr [CLI] auth login --profile workspace --use-device-code
        	            	-Error: device code login is not enabled for this host
        	            	+Error: device code login is not enabled for this workspace
        	            	 
        	            	@@ -17,3 +17,3 @@
        	            	 >>> DATABRICKS_DISCOVERY_URL=[DATABRICKS_URL]/oidc/accounts/spog-acct-123/.well-known/oauth-authorization-server musterr [CLI] auth login --host [DATABRICKS_URL]?a=spog-acct-123 --profile test --use-device-code
        	            	-Error: device code login is not enabled for this host
        	            	+Error: --use-device-code is only supported for workspace hosts
        	            	 
        	Test:       	TestAccept/cmd/auth/login/device-code/unsupported-host
        	Messages:   	cmd/auth/login/device-code/unsupported-host/output.txt vs /tmp/TestAcceptcmdauthlogindevice-codeunsupported-host4213060088/002/output.txt

latest (v1.26.0): same output as main (9175b8f)

@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Collaborator

✅ Integration test report

Commit: 7bde7ae

Run: 44300403810

Env 💚​RECOVERED ✅​pass 🙈​skip Time
💚​ aws linux-2core-8gb 1 272 23 8:44
💚​ aws-windows-latest-4core-16gb 1 274 21 8:56
💚​ azure linux-2core-8gb 1 271 23 8:40
💚​ azure-windows-latest-4core-16gb 1 273 21 14:08
💚​ gcp linux-2core-8gb 1 272 23 8:11
💚​ gcp-windows-latest-4core-16gb 1 274 21 7:57
Test Name aws linux-2core-8gb aws-windows-latest-4core-16gb azure linux-2core-8gb azure-windows-latest-4core-16gb gcp linux-2core-8gb gcp-windows-latest-4core-16gb
💚​ TestAccept 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
Top 11 slowest tests (at least 2 minutes):
duration env testname
4:30 azure-windows-latest-4core-16gb TestAccept
4:30 azure-windows-latest-4core-16gb TestFilerReadDir/workspace_files_extensions
3:27 aws-windows-latest-4core-16gb TestAccept
3:18 gcp-windows-latest-4core-16gb TestAccept
3:15 azure-windows-latest-4core-16gb TestFilerRecursiveDelete/workspace_files
3:03 gcp-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsReadDir
2:22 azure-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsRead
2:08 aws-windows-latest-4core-16gb TestFilerReadDir/workspace_files_extensions
2:07 azure-windows-latest-4core-16gb TestSyncFullFileSync
2:04 azure-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsReadDir
2:01 aws-windows-latest-4core-16gb TestFilerRecursiveDelete/workspace_files_extensions

maksim-zuev-db and others added 5 commits November 17, 2026 08:40
No remaining flag needs the comparison with the default, which was added for
--skip-workspace.

Co-authored-by: Isaac <no-reply@databricks.com>
The filter missed the account-scoped device authorization path.

Co-authored-by: Isaac <no-reply@databricks.com>
testserver.New registered the default /.well-known/databricks-config handler
before any test stub, and the router keeps the first registration, so test.toml
overrides of that path were ignored. Register it as a fallback that serves only
requests no other handler matches.

Co-authored-by: Isaac <no-reply@databricks.com>
The fake server's default host metadata has a workspace ID, so the account
login saved one and never reached the account-level path. Serve unified host
metadata without it.

Co-authored-by: Isaac <no-reply@databricks.com>
The token endpoint of account and unified hosts depends on the account ID,
so a pending login started for one account would send its device code to
another account's token endpoint. Store the account ID with the pending
login and reject a completion with a different one, like a different host.

Co-authored-by: Isaac <no-reply@databricks.com>
@maksim-zuev-db
maksim-zuev-db marked this pull request as ready for review November 17, 2026 22:09
@maksim-zuev-db
maksim-zuev-db requested review from a team as code owners November 17, 2026 22:09

@review-oss-bot review-oss-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me — no issues found.

@maksim-zuev-db
maksim-zuev-db requested review from mihaimitrea-db and simonfaltum and removed request for rauchy and rugpanov November 18, 2026 10:00

@simonfaltum simonfaltum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated review from simonfaltum's review agent (pr-review skill) at 3a2bb24. Each finding was verified against the code; simonfaltum may follow up.

No blocking issues found, approving. 8 non-blocking comment(s) and 2 question(s) below.

This PR lets auth login --use-device-code work with account and unified hosts. It fetches the account OIDC discovery document for classic account hosts and also checks the account ID when completing a non-interactive login. The core logic looks right and CI is green: the OAuth argument type checks don't overlap, and pending logins saved by earlier versions stay compatible. Nothing blocks the merge. The main suggestions are a unit test for the account-ID branch, and keeping the completion step from opening the workspace picker when it runs in a terminal. The rest are doc and comment nits, plus two non-blocking questions about the test-server fallback and the classic-account endpoints.

Questions

  1. HandleFallback exists so that per-test [[Server]] stubs can override the default /.well-known/databricks-config. .agents/rules/testing.md asks to model behavior in libs/testserver/ and to keep [[Server]] for routes the test server doesn't model. The change also makes the existing stub in acceptance/cmd/auth/profiles/spog-account/test.toml take effect for the first time; until now the default registered in testserver.New shadowed it. That test's output didn't change, but it now runs as a SPOG host. Would you rather make unified-host metadata a test server option, note the side effect in the description, or move the router change to its own PR? (non-blocking)
  2. For classic account hosts, deviceCodeConfig fetches the account discovery document but takes only device_authorization_endpoint from it, and keeps the token URL built by GetAccountOAuthEndpoints. The unified path uses the fetched document for every endpoint. Would it be simpler and more consistent to build the device code config from the fetched document's endpoints for classic accounts too? (non-blocking)

Accepted answers

  • Why re-merge setHost/setAccountID into setHostAndAccountId

Comments outside the changed lines

  • [nice to have] cmd/auth/login.go:492: --confirmation-code sets nonInteractive, but after the token exchange shouldPromptWorkspace → promptForWorkspaceSelection checks only IsPromptSupported. Now that account and unified hosts are allowed, an account-level login (--host "https://<spog>?a=<id>") completed in a terminal (as in the docs, where only step 1 uses < /dev/null) calls the workspaces API and blocks on a picker. Without a TTY, the same step only prints a hint. setHostAndAccountId can likewise prompt for the account ID in step 2. Consider skipping the workspace picker when nonInteractive (print the hint instead), the same way --configure-cluster is rejected for this mode.
  • [nit] docs/device-code-login.md:140: This row (... was started with a different host (or client ID, or scopes)) and the cmd/auth/README.md:154-157 paragraph ("The second step also checks the host, client ID and scopes...") both predate the new account ID check in changedSetting. A user who completes an account or unified-host login with a different ?a= or --account-id gets an error neither one lists. Add the account ID to both.
  • [nit] docs/device-code-login.md:134: "the workspace then discards the login" (line 132) and "in this workspace" (line 134) now apply to accounts too. Also, "Each profile, or host without a profile, has one pending login" (line 108) is now per host and account for account or unified hosts without a profile, because the key is <host>/oidc/accounts/<id>. Reword these lines.
  • [nit] libs/testserver/router.go:32: The type doc still says AddDefaultHandlers "installs fallback handlers that any test stub for the same pattern can override" (first-wins). HandleFallback adds a second "fallback" with different precedence: it loses to any exact or wildcard route, whatever the registration order. Mention HandleFallback in the type doc, and say when to use which.

Comment thread cmd/auth/login_device_code.go Resolved
Comment thread cmd/auth/login.go Resolved
Comment thread libs/auth/u2m/device_code.go Resolved
Comment thread libs/auth/u2m/device_code_test.go Resolved
maksim-zuev-db and others added 6 commits November 18, 2026 11:54
Co-authored-by: Isaac <no-reply@databricks.com>
…lier

Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
The second step of a device code login can run in a terminal. For an
account-level login on a unified host it then listed the workspaces and
waited on a picker, although the non-interactive login never prompts.

Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
@maksim-zuev-db

Copy link
Copy Markdown
Member Author

Thanks for the review!

Q1. Good catch on spog-account. Its stub was shadowed before, so the test never ran as SPOG, and its output didn't change. I'll note that in the description. I kept the stub because host metadata is a static fact about a host, not stateful API behavior. The router fix is its own commit (5032495), and the Router doc now covers HandleFallback (7bde7ae). I can move both into a separate PR if you prefer.

Q2. On the classic-account endpoints: agreed that using the fetched document would be more consistent with unified hosts. Browser login and token refresh build these endpoints with GetAccountOAuthEndpoints, though. Switching only device code login would give one profile two sources for its token URL. I'd rather make GetAccountOAuthEndpoints read the discovery document for all flows in a follow-up PR.

@maksim-zuev-db
maksim-zuev-db added this pull request to the merge queue Nov 18, 2026
Merged via the queue into main with commit 934ffd3 Nov 18, 2026
27 checks passed
@maksim-zuev-db
maksim-zuev-db deleted the device-code-account-hosts branch November 18, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants