Files
computer-playbook/roles/web-app-wazuh/files/playwright/playwright.spec.js
kevinveenbirkenbachandClaude Opus 5.5 163edebf01 refactor(web-app-wazuh): drop the Tor dual-stack workarounds
Wazuh carries no network-specific code any more: the onion front-proxy include, WAZUH_DASHBOARD_ONION_DOMAIN, the forked templates/proxy.conf.j2 vhost and the tor exclusive/primary overrides are gone. The role follows the Tor provider default like every other role with a Tor bond; serving one role on several networks returns generically in the multi-network change.

Without the forked vhost nothing forwards X-Forwarded-Host, so the dashboard OIDC redirect base is the static canonical url.base instead of trust_dynamic_headers.

Also: the dashboard port is read from one variable, the Playwright specs share wazuhLoginViaOidc and withBiberInGroup and assert worker-src blob:, PR-added explanatory comments are removed, and the root README lists the role.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-06 05:15:16 +00:00

11 lines
330 B
JavaScript

const { test } = require("@playwright/test");
const testBaseline = require("./test-baseline");
const testRbacRoles = require("./test-rbac-roles");
require("./test-csp");
test.describe.serial("wazuh: biber Keycloak group membership (single-owner)", () => {
testBaseline.registerBiberBaseline();
testRbacRoles.register();
});