da-auth

Obtains and caches Adobe IMS access tokens for DA Admin API calls.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aemgdc/aemdev --skill da-auth-aemgdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: da-auth
Source: https://github.com/aemgdc/aemdev/tree/main/.agents/skills/da-auth
Command: npx skills add https://github.com/aemgdc/aemdev --skill da-auth-aemgdc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires da-auth-helper.

What problem does it solve? Calling the DA (Document Authoring) Admin API at admin.da.live requires a valid Adobe IMS access token, and manually handling the OAuth flow, token caching, and expiry checks is repetitive and error-prone. This Skill automates token acquisition so other workflows can call the DA API without re-authenticating every time. ## Core Features & Use Cases - Cached Token Reuse: Checks ~/.aem/da-token.json for a valid cached token before triggering any browser login, avoiding unnecessary OAuth flows. - Multiple Auth Paths: Supports the da-auth-helper CLI (preferred), a DA MCP server, or manual token paste as a fallback for headless or restricted environments. - Token Verification: Validates the token against the DA Admin API with an HTTP status check before handing it off to the calling workflow. - Use Case: Before pushing authored HTML content to a DA repository, run this Skill to populate DA_TOKEN, then proceed with the content push knowing the token is verified and valid. ## Quick Start Get me a valid DA access token so I can push content to my org's DA repository.

Frequently Asked Questions about da-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an Adobe IMS access token for the DA API?▼

Run the da-auth-helper CLI via npx github:adobe-rnd/da-auth-helper token, which opens a browser for Adobe IMS login and prints the token to stdout. The token is cached at ~/.aem/da-token.json for reuse in later calls.

How long is a DA access token valid?▼

DA tokens are valid for roughly one hour, with a 60-second buffer applied when checking the cached token's expiry. If the cached token has expired, the OAuth login flow runs again to obtain a fresh one.

Can I authenticate to admin.da.live without a browser?▼

Yes, in headless environments you can use a DA MCP server's authentication tool if one is configured, or manually paste a token copied from the Authorization header of an admin.da.live request in your browser's DevTools.

Why does the DA API return 401 or 403 after authentication?▼

A 401 means the token expired between steps, so re-run the login flow to refresh it. A 403 means the authenticated user lacks permissions for that org or repo, so verify your DA access rights for the target repository.

When should I not run the DA authentication step?▼

Skip it when a valid DA_TOKEN already exists from earlier in the same session, when the create-site skill is handling auth in its own flow, or when a DA MCP server is active and provides its own authentication tool.