@Permission#

com.palmyralabs.palmyra.base.annotations.Permission

Declares the permission keys required to invoke a handler’s operations. Target: TYPE. Retention: RUNTIME.

Use cruds to assign a single permission across all CRUD operations, or set per-operation keys individually.

How these keys are evaluated#

Palmyra feeds each @Permission value through the standard Spring PermissionEvaluator registered in the application context — the same mechanism @PreAuthorize("hasPermission(...)") uses. This makes the authorization policy pluggable at the framework level:

• With the default PalmyraPermissionEvaluator (shipped by palmyra-dbacl-mgmt), the keys resolve against the ACL tables.
• Register your own PermissionEvaluator bean — Keycloak/OPA bridge, in-house RBAC, remote SaaS — and the same @Permission keys resolve through your policy engine without touching handler code.

Attributes#

Example#

@Component
@CrudMapping(value = "/v1/admin/user", type = User.class)
@Permission(
    value  = "USER",
    query  = "USER_READ",
    create = "USER_CREATE",
    update = "USER_UPDATE",
    delete = "USER_DELETE",
    export = {"USER_EXPORT"}
)
public class UserCrudHandler implements CrudHandler {
}