judo-runtime:permission-checking

Explain JUDO permission checking for CRUD operations and authorizer architecture.

Updated May 5, 2022
One-click install
npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill judo-runtime-permission-checking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: judo-runtime:permission-checking
Source: https://github.com/BlackBeltTechnology/judo-runtime-core/tree/main/judo-runtime-core-accessmanager/src/main/resources/claude/plugins/judo-accessmanager/skills/permission-checking
Command: npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill judo-runtime-permission-checking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive understanding of JUDO's permission checking mechanism, enabling developers to secure their applications by controlling access to data and operations.

Core Features & Use Cases

  • CRUD Permissions: Detailed explanation of how CREATE, UPDATE, and DELETE permissions are enforced.
  • Authorizer Architecture: Visualizations and explanations of the different authorizer types and their roles.
  • Debugging Authorization Failures: Guidance on identifying and resolving permission-related issues.
  • Use Case: When a user reports they cannot update a specific record, this Skill helps diagnose whether the issue lies in missing UPDATE flags, incorrect SignedIdentifier usage, or improper exposedBy annotations.

Quick Start

Explain how to check if a user has permission to create a new instance of the 'Customer' entity.

Frequently Asked Questions about judo-runtime:permission-checking

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

FAQPage Schema
How does JUDO permission checking work for CRUD operations?

JUDO permission checking enforces CRUD operations through an authorizer architecture that evaluates permission annotations, SignedIdentifier values, and exposedBy references to determine access control for CREATE, UPDATE, DELETE, LIST, and reference requests.

How do I debug authorization failures when a user cannot update a record?

Debug authorization failures by checking for missing UPDATE permission flags, verifying correct SignedIdentifier usage, and validating that exposedBy annotations are properly configured to allow the specific CRUD operation.

What is the role of SignedIdentifier in JUDO access control?

SignedIdentifier plays a critical role in JUDO access control by providing verified identity context that the authorizer architecture uses to evaluate permission annotations and determine if CRUD operations should be allowed.

How do I check if a user has permission to create a new entity instance?

Check user permissions for creating a new entity instance by verifying that the appropriate CREATE permission annotations are configured and that the SignedIdentifier is correctly validated through the JUDO authorizer architecture.

Why are my permission annotations not granting the expected access?

Permission annotations may fail to grant expected access due to incorrect exposedBy references, missing CRUD operation flags, or improper SignedIdentifier configuration that prevents the authorizer from validating the request.

Can I secure LIST and reference operations with granular permissions in JUDO?

Yes, JUDO supports granular permissions for LIST and reference operations through specific authorizer logic that evaluates permission annotations and SignedIdentifier context to control access to these operations.