user-management

Manage user lifecycles, identity policies, and password controls for multi-tenant environments.

7|1|Updated Feb 12, 2023
One-click install
npx skills add https://github.com/hirokazu-kobayashi-koba-hiro/idp-server --skill user-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-management
Source: https://github.com/hirokazu-kobayashi-koba-hiro/idp-server/tree/main/.claude/skills/user-management
Command: npx skills add https://github.com/hirokazu-kobayashi-koba-hiro/idp-server --skill user-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ユーザー管理機能の開発・修正を行う際に、ユーザー登録、IDポリシー、preferred_username の自動割り当て、ユーザーステータス、パスワードポリシーの実装を支援します。

Core Features & Use Cases

  • ユーザー登録: 直接登録と Federation 経由登録を扱う。
  • IDポリシーと preferred_username: テナントのポリシーに基づき自動割り当てと一貫性を確保。
  • ステータスライフサイクル: UNREGISTERED → REGISTERED → VERIFIED → LOCKED/DISABLED/DELETED の遷移を管理。
  • パスワードポリシー: NIST SP 800-63B準拠の検証と適用。

Quick Start

Register a new user and apply the identity policy to auto-assign preferred_username.

Frequently Asked Questions about user-management

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

FAQPage Schema
How do I manage user lifecycle status transitions in a multi-tenant environment?

User lifecycle management handles status transitions from UNREGISTERED through REGISTERED and VERIFIED to LOCKED, DISABLED, or DELETED states. This ensures consistent identity policy enforcement across tenant-bound services throughout the entire user lifecycle.

What password policy validation standard does this user management approach follow?

Password policy validation follows the NIST SP 800-63B standard, applying verification and enforcement rules during user registration and password updates. This ensures password controls meet recognized security guidelines for identity management.

How do I auto-assign preferred_username based on tenant identity policies?

Auto-assigning preferred_username uses tenant-specific identity policies to generate and enforce consistent username assignments. This applies during both direct registration and Federation-based registration flows within the multi-tenant architecture.

Can I handle both direct user registration and Federation-based onboarding?

User registration supports both direct registration and Federation-based onboarding paths. Both methods apply tenant identity policies for preferred_username assignment and enforce password controls within the same modular core architecture.

When should I implement separate identity policies versus password policies for user onboarding?

Identity policies govern preferred_username assignment and tenant consistency, while password policies enforce NIST SP 800-63B validation rules. Both are applied during onboarding but serve distinct enforcement purposes within the modular user management architecture.