Skip to content

Enable test_spog_workspace_google_credentials #1450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hectorcast-db merged 1 commit into from
May 28, 2026
Merged

Enable test_spog_workspace_google_credentials #1450

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions tests/integration/test_unified_profile.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,12 +87,6 @@ def test_spog_workspace_azure_client_secret(isolated_env):

# Environment: gcp-prod-ucacct
def test_spog_workspace_google_credentials(isolated_env):
# google-credentials uses a GCP ID token with target_audience=cfg.host.
# On the unified host this produces the same token for both account and workspace
# requests (identical OIDC exchange, identical audience). Account-level APIs accept
# this token, but workspace-level APIs return 401. The X-Databricks-Org-Id header
# is set correctly. This appears to be a server-side limitation on unified hosts.
pytest.skip("google-credentials ID token is rejected for workspace operations on unified hosts")
env = isolated_env("ucacct")
host = env("UNIFIED_HOST")
account_id = env("DATABRICKS_ACCOUNT_ID")
Expand Down
Loading