auth

Authenticate to the AEM Edge Delivery Services Config Service API via browser-based Adobe ID login.

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill auth-valithedge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/auth
Command: npx skills add https://github.com/valithedge/etisalatedge --skill auth-valithedge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines secure authentication for the AEM Edge Delivery Services Config Service API by launching a browser-based login flow to obtain and store an authentication token for subsequent API calls.

Core Features & Use Cases

  • Browser-based Adobe ID login to acquire an auth token with user consent.
  • Token persistence for reuse across multiple tooling steps requiring API access.
  • Use Case: generate configuration guides or perform admin tasks that must call the Config Service API without repeated logins.

Quick Start

Start by invoking the authentication flow to authenticate with your Adobe ID and retrieve an auth token for API calls.

Frequently Asked Questions about auth

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

FAQPage Schema
How do I authenticate with the AEM Edge Delivery Services Config Service API?

To authenticate with the AEM Config Service API, you launch a browser-based Adobe ID login flow to securely acquire and store an auth token for subsequent API calls.

Why does my AEM Config Service API call return a 401 error?

A 401 error from the AEM Config Service API indicates an expired or missing auth token, requiring you to refresh the token by completing the browser-based Adobe ID login flow again.

Do I need Node.js and Playwright to automate AEM API authentication?

Yes, automating AEM API authentication requires Node.js and Playwright to launch the browser environment and securely complete the Adobe ID login flow for token acquisition.

Can I reuse an AEM authentication token across multiple API tooling steps?

Yes, AEM authentication tokens are persisted after the initial browser login, allowing you to reuse the stored token across multiple tooling steps and API calls without repeated logins.

What is the best way to manage tokens for AEM Edge Delivery Services automation?

The best way to manage AEM Config Service tokens is using a browser-based authentication flow that captures, stores, and persists the auth token for reuse across automated workflows.

When should I not use a browser-based login flow for AEM API authentication?

You should avoid browser-based AEM API login flows in headless environments without GUI support, as the Adobe ID authentication process requires interactive user consent to generate the auth token.