[PrajwolAmatya]

Description

apiVault tests needs a user logged in with an acr=advanced (MFA step-up) token to request to /vault/graph. This step required headless Chromium (Playwright): log in via the web UI, switch to vault mode, scrape the TOTP QR code, and extract the token from browser storage. This step would only work for user roles Admin and Space Admin. In addition to that, the webUI steps takes more time to complete this flow and tests sometimes failed when decoding the QR code.

Key Changes:

• KeycloakHelper::getCode() now drives the whole login, including MFA, purely over HTTP.
• Renamed the authenticateKeycloakUserIfNeeded function to setUpKeycloakUserInOcis
• The step in vault.feature, And user "<user>" has logged in via web UI is replaced with And user "<user>" has been set up in oCIS, wihch uses the function setUpKeycloakUserInOcis to setup the user in oCIS.
• Removed WebUIHelper.php file and Playwright dependency.

With the changes the flaky test failure in apiVault with error Failed to base64-decode QR image data should be gone as we now don't rely on QR scanning step. Likewise, the test run time is reduced with the removal of web UI steps.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

[kw-security]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.