Andrea Cosentino created CAMEL-26846:
----------------------------------------
Summary: camel-cedar - validate embedded engine feasibility and
portability
Key: CAMEL-26846
URL: https://issues.apache.org/jira/browse/CAMEL-26846
Project: Camel
Issue Type: Task
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
h2. Problem / motivation
Cedar is a useful companion authorization engine for
principal/action/resource/context requests, but the official Java binding uses
JNI and native library packaging. Portability, concurrency and engine error
semantics need validation before committing to the component contract.
h2. Proposed scope
Prototype the released cedar-java binding in the supported Camel Java baseline.
Evaluate native loading on Linux/macOS/Windows targets, glibc versus musl,
architecture gaps and GraalVM/native-image feasibility. Benchmark policy/entity
parsing and evaluation; verify engine thread safety and whether parsed state
can be reused. Record an ADR with dependency/license/native packaging decisions.
h2. Acceptance criteria / validation
* Record supported/unsupported targets and actionable startup errors.
* Validate basic permit/deny, forbid precedence, malformed policies/entities
and evaluation diagnostics.
* Distinguish Cedar skip-on-error semantics from a proposed strict enforcement
mode.
* Establish concurrency and lifecycle strategy and a reproducible CI/test
approach.
* Separate any AWS managed-service integration from embedded Cedar.
h2. References
* https://github.com/cedar-policy/cedar-java/releases/tag/v4.11.0
* https://github.com/cedar-policy/cedar-java/blob/v4.11.0/CedarJava/build.gradle
* https://docs.cedarpolicy.com/auth/authorization.html
Source: read-only component audit at 5686684cb418. Recheck current main before
implementing; historical references identify the audited code.
_AI-generated by Codex on behalf of oscerd (JIRA: acosentino)._
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
