메뉴
This skill should be used when implementing "SAP login", "IDP redirect chains", "SSO configuration", "certificate-based authentication", or "BTP SAML2/IAS" in Playwright tests. Covers basic form auth, Office 365 SSO, API keys, multi-tenant, and mTLS.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
This skill should be used when "bridge injection fails", "control discovery returns empty", "window.__praman_bridge is undefined", or "UI5 module loading times out". Covers the 3-tier getById resolution, polling mechanism, and manual bridge diagnostics.
This skill should be used when an agent needs to issue "playwright-cli" commands, "run-code" browser scripts, "snapshot" accessibility trees, or manage "session state" with state-save/state-load. Mandatory reading before any CLI interaction with SAP apps.
This skill should be used when testing "Fiori Elements" apps, "List Report", "Object Page", "Analytical List Page", or "Overview Page". Covers SmartFilterBar, SmartTable, ObjectPageLayout, DynamicPage patterns, and the FE test library API.
This skill should be used when testing "FLP navigation", "semantic object deep links", "tile-based navigation", "WorkZone frame switching", "cross-app navigation", or "browser history" in SAP Fiori Playwright tests.
This skill should be used when testing "OData V2" or "OData V4" service calls, "reading model data", "intercepting batch requests", "seeding test data", or "verifying CSRF tokens" in SAP Playwright tests.
This skill should be used when "finding UI5 controls", "interacting with controls", "asserting control state", or working with "selector syntax", "SmartField inner controls", or "custom matchers". Covers id, controlType, properties, bindingPath, ancestor selectors and core Praman fixture methods.
| name | sap-authentication |
| description | This skill should be used when implementing "SAP login", "IDP redirect chains", "SSO configuration", "certificate-based authentication", or "BTP SAML2/IAS" in Playwright tests. Covers basic form auth, Office 365 SSO, API keys, multi-tenant, and mTLS. |
| version | 0.1.0 |
Select the authentication strategy based on the SAP landscape:
| Landscape | Strategy | Handler Config Key |
|---|---|---|
| SAP OnPrem | basic | username + password |
| BTP Cloud Foundry | btp-saml | IAS/SAML2 redirect |
| Azure AD SSO | office365 | OAuth2 code flow |
| API-only access | custom | API key / bearer |
| Certificate auth | custom | mTLS + client cert |
Use Playwright project dependencies to run authentication once and share state across tests.
Configure playwright.config.ts with a setup project that depends on nothing and produces storageState. All test projects depend on this setup project.
Create auth-setup.ts using SAPAuthHandler:
test as setup from playwright-praman.SAPAuthHandler with page and pramanConfig.auth.handler.login() which auto-detects the login form and IDP redirects.page.context().storageState({ path: '.auth/session.json' }).Store credentials in .env.test (gitignored, never committed):
SAP_CLOUD_BASE_URL -- system base URLSAP_CLOUD_USERNAME -- login usernameSAP_CLOUD_PASSWORD -- login passwordSAP_CLIENT -- SAP client number (optional)SAP_IDP_HOST -- custom IDP hostname (optional, for BTP SAML)Load via dotenv or Playwright's built-in env config.
For multi-tenant BTP apps, set the tenant subdomain in SAP_CLOUD_BASE_URL. The auth handler follows the IAS redirect chain automatically. Pass tenant in auth config for explicit tenant selection.
Store storageState at .auth/session.json. Playwright reuses cookies and local storage across tests in the same project, eliminating redundant logins. Regenerate on CI by running the setup project before test projects.
When Praman fixtures are unavailable (e.g., playwright-cli browser context during exploration), use raw Playwright auth. Detect the login form by checking for known input selectors and IAS hostnames, fill credentials via CLI commands, and wait for sap.ui.getCore to confirm UI5 loaded. See examples/raw-seed-auth.ts.
Refer to examples/ for complete auth setup patterns per strategy.