auth

You can fetch an auth token for the AEM Config Service API by running a Playwright-driven flow that opens an Adobe ID login window and captures the resulting token upon closure for project config storage.

Browser-based authentication captures API tokens by launching a login window for user credentials, intercepting the token generated upon window closure, and validating it via a lightweight API check before storage.

Using Playwright is required to automate Adobe ID login for API access because the authentication flow depends on a Playwright-driven browser process to open the login window and capture the auth token upon closure.

Validating an AEM authentication token before API requests is best done by performing a lightweight API check immediately after capturing the token from the browser login flow to confirm access.

Storing the browser-based authentication token in the project config is necessary to enable reuse across related skills and workflows without requiring repeated Adobe ID logins for subsequent API requests.

A browser-based login for the AEM Edge Delivery Services Config Service is required when preparing guides or documentation that require authenticated API access and valid tokens for tooling.