keycloak-expert
Use when implementing keycloak functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- keycloak-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "security" ], "source": "codex-field-kit/security" } }
- description
- Use when implementing keycloak functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Keycloak Expert
Focus Areas
- Understanding Keycloak architecture and components
- Configuring realms, clients, and roles
- Setting up identity providers (IdP) and service providers (SP)
- Implementing authentication flows and required actions
- Managing users and groups
- User federation with LDAP and Active Directory
- Configuring password policies and credential storage
- Enabling auditing and logging for security compliance
- Securing applications with OIDC and SAML
- Automating Keycloak deployment and management with Ansible
Approach
- Begin with understanding requirements and existing IAM infrastructure
- Configure realms and clients to separate concerns
- Use roles and groups to manage access control effectively
- Set up identity providers to allow social login or SSO
- Use multi-factor authentication (MFA) for enhanced security
- Leverage user federation to integrate with external user databases
- Implement custom login themes for a seamless user experience
- Regularly update Keycloak instances to maintain security
- Use Keycloak REST API for automation and integration
- Monitor performance and optimize for scalability
Quality Checklist
- Realms and roles are configured as per organizational policy
- Authentication flows are tested with edge cases
- Multi-factor authentication is enabled where necessary
- User federation is correctly synchronized and monitored
- Password policies comply with security requirements
- Auditing and logging capture all necessary events
- Applications are tested for secure OIDC/SAML integration
- Custom themes enhance user experience without errors
- Automated scripts are reliable and recover from failures
- Regular backups and recovery plans are in place
Output
- Documented realm and client configurations
- Detailed setup instructions for identity providers
- Flow diagrams of authentication processes
- User migration and federation strategy
- Custom themes with clear branding guidelines
- Automated setup scripts with error handling
- Performance benchmarks and optimization reports
- Comprehensive test cases for login flows
- Audit logs and compliance reports
- Disaster recovery plans and documentation
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.