Design and validate authentication and authorization architectures across web, mobile, and API systems.
npx skills add https://github.com/truongnat/skills --skill auth-pro
Please help me install this Agent Skill. Skill: auth-pro Source: https://github.com/truongnat/skills/tree/main/skills/auth-pro Command: npx skills add https://github.com/truongnat/skills --skill auth-pro
Professional guidance for designing and validating secure authentication and authorization across web, mobile, and API systems. It covers identity flows, credential and token lifecycle, session/JWT/OAuth/OIDC/API-key patterns, and policy enforcement models (RBAC/ABAC/ReBAC).
Ask me to design a secure authentication and authorization architecture for a multi-platform system, including token workflows and policy enforcement.
High-intent search queries and answers about installing and using this skill.
Designing secure authentication and authorization for web and mobile APIs requires selecting appropriate identity flows, hardening token lifecycles, and enforcing server-side policies using protocols like OAuth, OIDC, and JWT to prevent unauthorized access.
Choosing between RBAC, ABAC, and ReBAC depends on your access control complexity: RBAC handles role-based permissions, ABAC evaluates attribute-driven policies, and ReBAC models relationship-based access for complex authorization architectures.
Harden JWT and OAuth token lifecycles by implementing proper method selection, server-side enforcement, and MFA considerations, ensuring secure token generation, validation, and revocation across your authentication system to mitigate threat modeling risks.
Yes, mTLS and API keys are valid authentication patterns for multi-platform systems, often integrated alongside SAML and OAuth/OIDC to secure web, mobile, and API surfaces through method selection and server-side enforcement.
You need OAuth and OIDC instead of basic API keys when designing decentralized authentication architectures that require delegated access, identity verification, and complex token lifecycle management across web and mobile platforms.
SAML limitations in modern API authentication architectures include heavier XML payloads and reduced suitability for mobile platforms compared to JWT and OAuth/OIDC, making it better suited for enterprise web identity flows rather than lightweight API token systems.
ilyvscSet up Better Auth authentication for NestJS and Next.js with Drizzle ORM and PostgreSQL.
sigitpoerwoAudit and harden software security across DevSecOps pipelines.
GGEduHarden Django applications with production security configurations and secure coding practices.
myapihqCreate OIDC identity providers and configure RS256 token verification.
