auth-core

Update Madoc TS authentication server and register Passport provider strategies.

57|15|Updated Nov 28, 2018
One-click install
npx skills add https://github.com/digirati-co-uk/madoc-platform --skill auth-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-core
Source: https://github.com/digirati-co-uk/madoc-platform/tree/main/.agents/skills/auth-core
Command: npx skills add https://github.com/digirati-co-uk/madoc-platform --skill auth-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Updating and extending the Madoc TypeScript authentication server and its Passport-based provider strategies can be complex and error‑prone, making it difficult to safely add new auth providers or modify login behavior.

Core Features & Use Cases

  • Auth server verification: Handles token validation and endpoint security.
  • Passport strategy registration: Adds, configures, and merges new OAuth providers.
  • Provider login flow: Manages federated user lookup and JWT‑cookie integration.
  • Use case: Quickly integrate a new OAuth provider (e.g., GitHub or Google) into the Madoc TS platform without breaking existing authentication flows.

Quick Start

Use the auth-core skill to add a new OAuth provider to the Madoc TS authentication server.

Frequently Asked Questions about auth-core

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

FAQPage Schema
How do I add a new OAuth provider to a TypeScript authentication server?

Adding a new OAuth provider involves registering a new Passport strategy and adjusting the provider login flow for federated user lookup. This updates the TypeScript authentication server to handle the new provider without breaking existing flows.

How does Passport strategy registration work for federated user lookup?

Passport strategy registration adds, configures, and merges new OAuth providers into the authentication server. It manages provider login flow by mapping provider emails to existing users and integrating JWT-cookie sessions for seamless access.

Can I modify token verification endpoints in a Madoc TS authentication server?

Yes, you can modify auth server verification endpoints to handle token validation and endpoint security. This ensures token verification and provider email mapping integrate seamlessly with existing Madoc services.

What's the best way to integrate Google OAuth login into an existing TypeScript platform?

The best way is to register a new Passport strategy for Google OAuth and adjust the provider login flow. This handles federated user lookup and JWT-cookie integration while preserving existing authentication server behavior.

Why does adding a new auth provider break existing login flows in a TypeScript server?

Existing login flows break when new Passport strategies are not properly merged or token verification endpoints are misconfigured. Correctly registering the strategy and adjusting provider email mapping prevents disrupting the authentication server.

Do I need an existing Madoc TS authentication server to use this auth-core Skill?

Yes, this Skill is designed to update and extend the existing Madoc TypeScript authentication server. It modifies verification endpoints and Passport provider strategies within the current Madoc environment.