test(login-flow): use Astrolabe's client id for management API tests
The previous commit moved `mcp-login-flow`'s `ALLOWED_MGMT_CLIENT` to `astrolabeMcpClientOAuth00000000000` so production-shaped Astrolabe traffic actually validates. Update the management API test fixture to match: the static OIDC client created in `tests/server/login_flow/conftest.py:login_flow_static_client_credentials` now uses the same id `app-hooks/before-starting/26-configure-astrolabe-oauth.sh` provisions in real deployments, so the test path exercises the same code as production rather than a substituted fixture-only id. `mcp-multi-user-basic`'s allowlist is unchanged (`nextcloudMcpServerUIPublicClient`) and the shared `configure_astrolabe_for_mcp_server` fixture in `tests/conftest.py` keeps that as its default, so multi-user-basic tests are unaffected. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.7
parent
fd8c037eea
commit
d83c32a9dd
@@ -1,9 +1,11 @@
|
||||
"""Integration tests for the management API on the login-flow MCP server.
|
||||
|
||||
These tests drive a real OAuth flow against Nextcloud's `oidc` app using the
|
||||
static `nextcloudMcpServerUIPublicClient` client (which is allowlisted on the
|
||||
`mcp-login-flow` container via `ALLOWED_MGMT_CLIENT`), then hit the
|
||||
management API endpoints with the resulting bearer token.
|
||||
static `astrolabeMcpClientOAuth00000000000` client (which is allowlisted on
|
||||
the `mcp-login-flow` container via `ALLOWED_MGMT_CLIENT` and matches the id
|
||||
provisioned by `app-hooks/before-starting/26-configure-astrolabe-oauth.sh`
|
||||
in real deployments), then hit the management API endpoints with the
|
||||
resulting bearer token.
|
||||
|
||||
Regression coverage for the bug where /api/v1/apps proxied to OCS v1
|
||||
/cloud/apps and always 401'd. The handler now uses /ocs/v2.php/cloud/capabilities,
|
||||
|
||||
Reference in New Issue
Block a user