vivreal-auth-architecture

Diagnose Vivreal authentication failures by differentiating API Gateway and portal cookies.

Updated May 12, 2026
One-click install
npx skills add https://github.com/HillBombCreations/vivreal-skills --skill vivreal-auth-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vivreal-auth-architecture
Source: https://github.com/HillBombCreations/vivreal-skills/tree/main/vivreal-infra/skills/vivreal-auth-architecture
Command: npx skills add https://github.com/HillBombCreations/vivreal-skills --skill vivreal-auth-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit aids in diagnosing and resolving authentication challenges related to the Vivreal stack, clarifying boundaries between authorization and signed-context management, and providing a comprehensive guide for troubleshooting and understanding the authentication flow.

Core Features & Use Cases

  • Authentication Boundary: Provides clear definitions between API Gateway authorizers and portal-signed cookies, reducing confusion around Vivreal's dual auth systems.
  • Debugging Assistance: Offers troubleshooting guidance for common issues like 401/403 errors, JWT claims, and active_ctx mismatches.
  • Use Case: When encountering issues with backend Lambda access due to authentication, use this Skill unit to differentiate between system issues and incorrect context handling.

Quick Start

Activate the vivreal-auth-architecture skill when you encounter authentication-related issues in your Vivreal stack. The skill will guide you through the diagnostic steps specific to the issue you're experiencing.

Frequently Asked Questions about vivreal-auth-architecture

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

FAQPage Schema
Why am I getting 401 and 403 authentication errors in my Vivreal stack backend?

401 and 403 errors in the Vivreal stack stem from authorization failures or incorrect context handling. Diagnosing them requires differentiating between API Gateway authorizers and portal-signed cookies to identify the exact token or context mismatch.

What is the difference between API Gateway authorizers and portal-signed cookies?

API Gateway authorizers and portal-signed cookies form a dual authentication boundary. API Gateway handles token validation like Cognito JWTs, while portal cookies maintain signed context for active session management.

How do I debug Cognito JWT parsing and active_ctx mismatches?

Debug Cognito JWT parsing and active_ctx mismatches by tracing the authentication flow through API Gateway and portal boundaries. This isolates whether backend Lambda access failures stem from system issues or incorrect context handling.

How do I fix backend Lambda access failures caused by authentication issues?

Fix backend Lambda access failures by clarifying the boundaries between authorization and signed-context management. Diagnose the dual auth systems to determine if the issue is an API Gateway authorizer or a portal cookie problem.

When should I check API Gateway authorizers versus portal cookies for context handling challenges?

Check API Gateway authorizers versus portal cookies when you encounter JWT claims or active_ctx mismatches. Clarifying the boundaries between authorization and signed-context management reduces confusion around the stack's dual auth systems.