authentik

Design, secure, and operate authentik-based OIDC integrations for production systems.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kittne/codex-skills-by-codex --skill authentik-kittne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authentik
Source: https://github.com/kittne/codex-skills-by-codex/tree/main/authentik
Command: npx skills add https://github.com/kittne/codex-skills-by-codex --skill authentik-kittne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design, secure, and operate authentik-based OIDC integrations for production systems. Use for application/provider setup, scopes and claims mapping, redirect URI policy, token/session lifetime decisions, signing key management, and incident-ready operations.

Core Features & Use Cases

  • Provider and Application Modeling: Create dedicated provider/app pairs, configure redirect URIs, and choose client_type to match threat model.
  • Scopes, Claims, and Subject Design: Define minimal default scopes, map claims, review subject strategies for downstream linking, and avoid claim overexposure.
  • Token, Session, and Operational Guardrails: Tune token lifetimes, rotate signing keys, validate logout endpoints, and monitor audit trails.
  • Operational Readiness: Monitor OIDC endpoints, rehearse recovery, document key rotation and incident runbooks.
  • Validation & Troubleshooting: Check JWKS availability and openid configuration, and verify environment-wide consistency.
  • Common Failure Modes: Redirect URI regex pitfalls, token misconfigurations, and inconsistent subject mappings.
  • Definition of Done & Checklists: Ensure least-privilege policies, reviewed claims, and documented recovery paths.
  • References: See references/authentik-2026-02-18.md for in-depth guidance.
  • Reference Index: rg commands for the reference file.

Quick Start

Deploy an authentik provider, configure a client with strict redirect URIs, map essential claims, and enable rotation and monitoring.

Frequently Asked Questions about authentik

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

FAQPage Schema
How do I configure authentik OIDC redirect URIs and client type for production?

To configure authentik OIDC for production, create dedicated provider/app pairs, set strict redirect URI policies, and choose a client_type matching your threat model. This ensures secure access control and prevents redirect URI regex pitfalls across environments.

What is the best way to map OIDC scopes and claims in authentik without overexposing data?

Mapping OIDC scopes and claims in authentik requires defining minimal default scopes, reviewing subject strategies for downstream linking, and validating claim exposure. This prevents claim overexposure and ensures consistent subject mappings across authenticated applications.

Why does my authentik OIDC token configuration fail across different environments?

Authentik OIDC token failures often stem from token misconfigurations, inconsistent subject mappings, or redirect URI regex pitfalls. Validate JWKS availability, check openid configuration endpoints, and ensure environment-wide consistency to resolve these issues.

How do I rotate authentik signing keys and manage token lifetimes securely?

Rotating authentik signing keys and managing token lifetimes involves tuning token lifetimes, validating logout endpoints, and executing key rotation procedures. This maintains operational readiness and secures session management against unauthorized access.

Does authentik OIDC integration support incident recovery and audit monitoring?

Authentik OIDC integration supports incident recovery by monitoring audit trails, rehearsing recovery procedures, and documenting incident runbooks. You get operational guardrails, endpoint monitoring, and repeatable recovery paths for production systems.