CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

adobe/aem-edge-delivery-services

Skills for building AEM Edge Delivery Services sites — site creation, block development, content modeling, code review, testing, and page import.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

SKILL.mdskills/da-auth/

name:
da-auth
description:
Use this to obtain, reuse, refresh or troubleshoot Adobe IMS authentication for Experience Workspace (formerly DA) content APIs: admin.da.live (DA) or api.aem.live (Source Bus). Use before pushing HTML content, listing documents or triggering a preview when no credential is known to work for that API, or for 401/403 (Unauthorized/Forbidden) and authentication checks where status 200 is insufficient. Not for choosing a content store or planning content changes when authentication already works.
license:
Apache-2.0
metadata:
{"version":"1.1.2"}

DA Authentication

Get an Adobe IMS token for the Experience Workspace (formerly DA) content APIs: the DA API or the Source Bus API. Callers can keep the name DA_TOKEN. Reuse credentials already accepted by the target API. If an authenticated MCP/backend already handles login, use that instead; do not assume it exposes a login tool.

Choose the API

Use the caller's known content source. If unclear, confirm the site configuration or ask the user: a populated DA listing can contain onboarding documents while the authored content lives in Source Bus. See da-content for content operations.

Content sourceProtected read example
DA (admin.da.live)https://admin.da.live/list/{{ORG}}/{{REPO}}/{{FOLDER}}
Source Bus (api.aem.live)https://api.aem.live/{{ORG}}/sites/{{SITE}}/source/{{PATH}}

Choose a known, existing protected folder or document. api.aem.live accepts eligible IMS Bearer tokens with aem.frontend.all or aem.backend.all; the helper requests aem.frontend.all. DA acceptance does not prove access to a Source Bus site.

Get or reuse a token

The helper caches access_token and expires_at (epoch milliseconds) in ~/.aem/da-token.json. It reuses unexpired tokens with a 60-second buffer; missing expiry triggers login. Do not assume a fixed token lifetime.

Replace {{READ_URL}} with the protected read above. Use the token in the same shell; never print, paste or commit it:

DA_TOKEN=$(npx github:adobe-rnd/da-auth-helper token) &&
  curl -sS -o /dev/null -w '%{http_code}\n' \
    -H "Authorization: Bearer $DA_TOKEN" "{{READ_URL}}"

The user completes browser sign-in and selects the IMS org that provides access. If login cannot run here, have the user run it locally; do not ask for a DevTools token.

Verify the API the caller will use. On api.aem.live, /status/ can return 200 anonymously, so it proves nothing. An auth_token cookie can override the Bearer header; test without auth cookies.

Recover from 401 or 403

SymptomCheck
401Token missing, invalid or expired, or IMS user lookup failed. Check the credential and target API; do not loop login.
403Account/org lacks access for that path/action. Ask which IMS org supplies the user's group access (not the URL's org); do not assume a new grant is needed.

Helper login and token both reuse an unexpired cache, even if rejected. To replace it:

npx github:adobe-rnd/da-auth-helper logout

This clears only the helper cache, not the browser session. Rerun the acquire-and- verify command, select the intended IMS org, and retry the same protected read. If 403 persists in the intended context, check path/action permissions; refreshing credentials does not add grants.

If the browser keeps the wrong account/org context, these alternatives restored access in live checks; neither is guaranteed to force an org chooser:

  • Private window: while the helper waits for its callback, open its printed public authorize URL in a private window and select the intended org. Leave the automatically opened normal-browser login unfinished. There is no incognito flag.
  • Switch in da.live: select the intended org in da.live, clear the helper cache, then rerun authentication. Switching da.live alone does not replace the helper's cached wrong-org token.

skills

da-auth

README.md

tile.json