slug: casdoor
provider: Casdoor
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 5
edges:
- tag: Authentication
  spec_file: casdoor-authentication-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.92
  evidence: POST /api/login "Login a user"; POST /api/signup "Sign up a new user"; POST /api/device-auth
    "OAuth 2.0 device authorization"
  reason: Operations perform user authentication, registration and OAuth device authorization — squarely
    identity and access management; no other reading fits.
- tag: Permissions
  spec_file: casdoor-permissions-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.9
  evidence: POST /api/enforce "Casbin enforcement check"; GET /api/get-permissions "List permissions"
  reason: Authorization policy listing and Casbin enforcement decisions are core access management; this
    is IAM rather than any entitlement-commerce capability since there is no subscription or plan context.
- tag: Users
  spec_file: casdoor-users-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.9
  evidence: POST /api/add-user "Create a user"; POST /api/check-user-password "Validate a user password"
  reason: User account lifecycle and credential validation in an IAM/SSO server is identity and access
    management, not customer or employee master data — the records are login principals with passwords.
- tag: Roles
  spec_file: casdoor-roles-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.85
  evidence: GET /api/get-roles "List roles"; POST /api/add-role "Create a role"
  reason: 'Role definition for role-based access control in an IAM server — identity and access management.
    Not HR job roles: the vendor describes ''role-based access control''.'
- tag: Applications
  spec_file: casdoor-applications-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.7
  evidence: '"Casdoor is an open-source IAM/SSO platform ... managing users, organizations, applications,
    roles, permissions"; GET /api/get-applications "List applications"'
  reason: In Casdoor an 'application' is an OAuth/OIDC client registration used to configure SSO, so these
    CRUD operations configure the identity and access management estate rather than any product/app portfolio
    business function. Mapped to Identity & Access Management, with moderate confidence because the operations
    themselves are generic CRUD.