cedar-policy

Install cedar-policy-cli 4.12.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/cedar-policy/cedar/releases/download/cedar-policy-cli-v4.12.0/cedar-policy-cli-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/cedar-policy/cedar/releases/download/cedar-policy-cli-v4.12.0/cedar-policy-cli-installer.ps1 | iex"

Download cedar-policy-cli 4.12.0

Fixed

• Fixed transitive closure computation for schemas with cyclic entity type hierarchies of length ≥ 3 (introduced in 4.11.0).

Full Changelog: v4.11.1...v4.11.2

Cedar Language Version: 4.5

Fixed

• Protobuf parsing for expression now error on encountering a like pattern element with multiple characters in a single PatternElem::Char instead of dropping the extra characters.
• Slot identifiers are now checked for JSON policy templates using slots in is Type in ?slot scope constraints. Loading a JSON format policy using principal is Type in ?resource or resource is Type in ?principal. (#2351)

Cedar Language Version: 4.5

Added

• Public syntax tree (pst) module for programmatic construction, inspection, and manipulation of Cedar policies. Accessible via to_pst() / try_into_pst() / from_pst() on Policy, Template, and PolicySet. try_into_pst() consumes the value to avoid cloning. TPE residual policies can be converted to PST for structured inspection of residual expressions. Third-party types used in PST fields (SmolStr, LinkedHashMap, NonEmpty) are re-exported from the pst module. (#816, #366)
• The Type-aware partial evaluation (TPE) experimental feature now supports template-linked policies. This would previously return a SlotNotSupportedError error. This error variant is removed and replaced with UnlinkedSlotError, occurring only when slot in a linked policy is not bound. (#2314).

Fixed

• Improved Cedar schema parse help for two common syntax mistakes: forgetting appliesTo before an action block, and adding ; after a namespace declaration. (#1043, #1044)
• FunctionArgumentValidation errors now include a help message describing the expected format for extension function arguments: decimal, ip, datetime, and duration. (#834)
• Serialization of residual policies with error() nodes does not fail, instead results in JSON with {"error": []}. (#2202)
• Fixed conversion from protobuf policy sets to public type for policy sets containing templates and template-linked policies. (#2330)
• Fixed deserialization from protobuf of entity and context attributes containing extension values. (#2344)

Cedar Language Version: 4.5

Added

• Extended has operator in JSON policies, maintaining backwards-compatible desugaring of extended has in Cedar policies to json (#1889).

Changed

• Explicit failure when using experimental features tolerant-ast and protobuf together: serialization of policies with error in action constraint fails (#2248, #2247).

Fixed

• Decoding entities with parents and indirect ancestors in protobuf (#2240).

Cedar Language Version: 4.4

Changed

• Minor optimizations to decimal parsing (#2156) and constructing constant identifiers (#1880).

Cedar Language Version: 4.4

Added

• Entity::attrs() and Entity::tags() to iterate over all attributes/tags of an Entity (#2084)
• to_json_value() methods on Entities, Context, and EntityUid (matching the existing one on Entity) (#2085)
• From or TryFrom impls for converting public types into their corresponding FFI versions in the ffi module (new impls on ffi::EntityUid, ffi::Context, ffi::Entities, ffi::Policy, ffi::Template, and ffi::StaticPolicySet) (#2085)
• schema_to_json_with_resolved_types() function, which takes in a Cedar schema and returns a json schema without any instances of EntityOrCommon; they're all either Entity or CommonType (#2058)
• More derives (PartialEq, Clone, etc) for a number of types in the ffi module (#2083)
• TPE: Simplify <residual> && false to false and <residual> || true to true when <residual> is error-free. (#2091)

Fixed

• Policy formatting for record literals and index-style attribute access. (#2117, fixing #959 and #1005)

Cedar Language Version: 4.4

Changed

• Deprecated entity-manifest experimental feature. Consumers of these functions should migrate to the tpe feature and use PolicySet::is_authorized_batch. (#1945)

Fixed

• Fixed authorization and other error messages to correctly display all diagnostic information. (#1944)

Cedar Language Version: 4.4

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 4.4

Added

• Added TpeResponse::residual_policies and TpeResponse::nontrivial_residual_policies to get residual policies under experimental feature tpe. (#1906)
• Added PartialEntity::new and PartialEntities::from_partial_entities to programmatically construct PartialEntity and PartialEntities under feature tpe. (#1916)

Changed

• For the tpe experimental feature, PartialEntities::from_concrete now requires a Schema and will validate the entities, ensuring that a PartialEntities object always meets the preconditions required for type aware partial evaluation. (#1903)
• Evaluate has operation when the LHS record is projectable during partial evaluation. (#1912)
• Deprecated schema parsing errors ActionAttributesContainEmptySet, UnsupportedActionAttribute, ActionAttrEval, and ExprEscapeUsed. These errors are never returned, so it is safe to delete any associated error handling code. (#1929)
• Made policy validation for in, ==, and hasTag slightly more permissive to match the formally verified Lean model. (#1931)
• Increase partial evaluation precision for if-then-else, or, and expressions (#1940)

Fixed

• Removed incorrect dependency of feature partial-eval of feature tpe. (#1898)
• Fixed incomplete policy ID renaming by PolicySet::merge. Updated policy IDs were correctly reflected when getting a policy with PolicySet::policy and PolicySet::template, but Policy::id, Template::id, and Policy::template_id continued to return the original id.
• Fixed issue where SchemaFragment::to_cedarschema could return a string that is not a valid Cedar schema.

Cedar Language Version: 4.4

Fixed

• Fixed parsing of small negative decimal literals. (#1966)

Cedar Language Version: 4.4

Added

• Added Schema::actions_for_principal_and_resource to list actions which apply to a particular principal and resource type.
• For the tpe experimental feature, added PolicySet::query_actions to list the actions which might be authorized given partial request with an unknown action.
• For the tpe experimental feature, added PartialEntities::empty to conveniently construct an empty partial entity set.

Cedar Language Version: 4.4

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 4.4

Fixed

• Fixed doc.rs build (#1878)

Cedar Language Version: 4.4

Added

• Added deep_eq to the Entity and Entities structs to allow comparing these objects for structural equality. (#1723)
• Added stateful_is_authorized, preparse_policy_set and preparse_schema to support stateful evaluation using a cached policy set and schema, in the ffi module. (#1831, fixing #1829)
• Added has_non_scope_constraint for Policy and Template, returning true if the policy or template has a when or unless condition. (#1852)
• Implemented variadic ipaddr.isInRange that returns true if the target ipaddr is in range for any of the arguments as described in RFC 99, under the experimental flag variadic-is-in-range. (#1775)
• Implemented type-aware partial evaluation as described in RFC 95, under the experimental flag tpe. (#1575)
• Implemented batched evaluation, also under the experimental flag tpe. Batched evaluation allows for permission queries against large databases of entities. (#1812)

Changed

• Bumped MSRV to 1.85 (#1683)

Cedar Language Version: 4.4

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 4.4

Added

• Added the ability to serialize Unknown values to JSON. Matching the format that is currently allowed for deserializing Unknown Values. (#1748)

Changed

• Allow multiple argument extension function calls in entity JSON format. (#1697)

Fixed

• Fixed multiple functions on Entities to correctly consider entity tags when determining whether two entities are identical. These functions will now only consider two entities identical if they have the same identifiers, attributes, ancestors, and tags. Attempting to create an Entities object where a duplicated entity identifier maps to two entities with different tags will now result in an error. Attempting to validate an action entity with any tags will always result in an error. This change specifically impacts from_entities, add_entities, add_entities_from_json_file, add_entities_from_json_value, and add_entities_from_json_str. (#1725)
• Fixed bug with template linked policies where previously, slots appearing within the is in operator were not correctly filled. This fix may cause some templates that would previously validate (in error) to no longer validate. (#1728)

Cedar Language Version: 4.4

Added

• Added Entities::upsert_entities() to add or update Entitys in an Entities struct (resolving #1479)
• Added schema parsing functions to improve compatibility with JSON schema originally writing for versions 2.5.0 and earlier. These functions will ignore unrecognized keys in some positions where they are currently an error, matching the behavior of earlier versions. This is intended help some users migrate to the current 4.0 schema format. The new functions are deprecated and placed behind the deprecated-schema-compat feature. (#1600)
• Expression::new_duration, Expression::new_datetime, RestrictedExpression::new_duration, and RestrictedExpression::new_datetime (#1614)
• Added a function to be able to split a policy set parsed from a single string into its component static policies and templates. The relevant function is policy_set_text_to_parts in the ffi module (#1629).
• Implemented RFC 71 (trailing commas) for Cedar policy files. (#1606)

Changed

• Allow entity attributes and tags to contain Action-typed entities, and pass policy/entity/request validation (#1652)
• Changed experimental entity-manifest function compute_entity_manifest to accept an &Validator instead of &Schema. Callers can construct a Validator from a schema with Validator::new afterwhich a reference to the original schema can be retrieved using Validator::schema. (#1584)
• Bumped MSRV to 1.82 (#1611)

Cedar Language Version: 4.3

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 4.3

Fixed

• Apply entity conformance checking to tags (#1604)

Cedar Language Version: 4.3

Added

• Stabilized RFC 76, removing the experimental level-validate feature flag. That functionality is now available without the feature flag. Stabilization comes with changes to fix bugs in the features. Level validation is now more permissive when checking if expressions (fixing #1507), and stricter when checking record literals and entity tag operations (fixing #1505 and #1503). (#1567)
• Implemented RFC 53 (enumerated entity types) (#1377)
• Stabilized RFC 80 (datetime extension), making datetime a default feature. (#1541)
• Added Entities::remove_entities() to remove Entitys from an Entities struct (#1453, resolving #701)
• Added PolicySet::merge() to merge a PolicySet into another PolicySet struct (#1476, resolving #610)
• Added to_cedar functions for PolicySet, Policy, and Template that render the policy in the Cedar syntax. These functions can be used to convert JSON formatted policies into the human-readable syntax (#1510, resolving #461)
• Added Validator::schema() to get a reference to the Schema even after it has been consumed to construct a Validator (#1524)
• Added Schema::request_envs() to get all of the RequestEnvs that are valid according to the schema. (This joins the existing Policy::get_valid_request_envs() and Template::get_valid_request_envs() that return the subset of request envs that are valid for a particular policy or template.) (#1547)
• Added EntityId::unescaped(), analogous to EntityId::escaped(). This is simply an alias for EntityId::as_ref() with the AsRef impl that produces &str. (#1555)
• Added PartialResponse::unknown_entities method (#1557)
• Added Entities::len and Entities::is_empty methods (#1562, resolving #1523)

Changed

• Changed Entities::add_entities and Entities::from_entities to ignore structurally equal entities with the same Entity UID.
• For protobufs experimental feature, a number of changes to the interface and the Protobuf format definitions, as we continue to iterate towards making this feature stable. (#1488, #1495, #1506, #1535)
• Bump MSRV to 1.81 (#1542)
• HierarchyNotRespected validation error is no longer returned (although the error variant remains, to avoid a breaking change). This means that in some edge cases, policies that previously failed to validate under strict validation will now pass validation, probably with an ImpossiblePolicy warning. (#1355, resolving #638)

Cedar Language Version: 4.2

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 4.2

Changed

• Significant changes to the API for the experimental protobufs feature (#1452, #1467, others)

Fixed

• Fixed the experimental protobufs feature so that code depending on cedar-policy with this feature now successfully builds, even if that code is not part of the same Cargo workspace as cedar-policy, cedar-policy-core, etc (#1452).
• Fixed a bug in the experimental entity-manifest feature. If an entity appears as both a possible value for a scope variable and an entity literal, slicing using entity manifests will now correctly capture all necessary attributes (#1429).
• Fixed a bug in the experimental entity-manifest and level-validate features. These features failed to consider any attribute accesses occurring inside the guard of an if expression when guard expression had a singleton boolean type (#1462).

Cedar Language Version: 4.2

Fixed

• Assume sufficient stack space when it cannot be determined (#1446, resolving #1443). Note that on platforms not supported by stacker (e.g., Wasm, Android), this means that large inputs may result in stack overflows and crashing the process. On all platforms supported by stacker (Linux, macOS, ...), Cedar will continue to return the graceful error RecursionLimit instead of crashing.

Cedar Language Version: 4.2

Fixed

• Disable doc generation for feature protobufs, unblocking that for other features (#1434)

Cedar Language Version: 4.2

Added

• Implemented RFC 62 (extended has operator) (#1327, resolving #1329)
• Implemented RFC 80 (datetime extension) as an experimental feature under flag datetime (#1276, #1415)
• Added new .isEmpty() operator on sets (#1358, resolving #1356)
• Implemented RFC 48 (schema annotations) (#1316)
• Implemented RFC 74 (entity manifests and slicing) behind the experimental entity-manifest flag (#1239)
• Added protobuf schemas and (de)serialization behind the experimental protobufs flag (#1277, #1345)
• New Entity::new_with_tags() and Entity::tag() functions (#1402, resolving #1374)
• Added Request::context and Context::get methods to allow easy extraction of values from the context by key (#1318)
• For the partial-eval experimental feature, added PartialResponse::reauthorize_with_bindings to accept substitutions from an iterator and deprecated PartialResponse::reauthorize (#1387)
• For the partial-eval experimental feature, added RequestBuild::unknown_principal_with_type and RequestBuild::unknown_resource_with_type methods, allowing an unknown principal or resource to be constrained to a certain entity type (#1391)
• Added Clone implementations for more types (#1324)

Changed

• Stopped emitting warnings for identifiers containing certain printable ASCII characters (e.g., / and :) (#1336, resolving #621)

Fixed

• Attach source code to certain errors so that miette::Reports derived from these errors are self-contained (#1351, resolving #977 and #1335)

Cedar Language version: 4.1

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language version: 4.1

Changed

• The error associated with parsing a non-existent extension function additionally includes a suggestion based on available extension functions (#1280, resolving #332).
• The error associated with parsing a non-existent extension method additionally includes a suggestion based on available extension methods (#1289, resolving #246).
• Improved entity validation speed, particularly for large schemas with many actions (#1290 and #1296, resolving #1285)

Fixed

• Some misleading parser errors for JSON schema with mistakes in nested attribute definitions (#1270, resolving #417)
• Cedar schema printer now correctly prints entity tags (#1304)

Cedar Language version: 4.1

Fixed

• Fixes a minor issues preventing documentation from building on docs.rs

Cedar Language version: 4.1

Added

• Added sub_entity_literals API (#1233).
• Added level validation RFC 76 as an experimental feature.
• Annotations without explicit values. It is now possible to write an annotation @my_annotation as short-hand for @my_annotation("") (#1231, resolving #1031).
• Stabilized RFC 82, removing the experimental entity-tags feature flag. That functionality is now available without the feature flag.

Changed

• The validator provides a more specific hint when an action ID cannot be found and the same action ID with Action:: has been defined (#1258, resolving #166)

Cedar Language Version: 4.0

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 4.0

Added

• Added get_entity_literals API (#1149).
• Implemented RFC 82, adding entity tags to the Cedar language under experimental flag entity-tags (#1204, #1207, #1213, #1218)
• Added public APIs to get language and SDK version numbers (#1219).

Fixed

• The formatter will now consistently add a trailing newline. (resolving #1217)

Cedar Language Version: 4.0

Added

• Additional functionality to the JSON FFI including parsing utilities (#1079) and conversion between the Cedar and JSON formats (#1087)
• (*) Schema JSON syntax now accepts a type EntityOrCommon representing a typename that can resolve to either an entity or common type, matching the behavior of typenames written in the human-readable (Cedar) syntax. (#1060, as part of resolving #579)

Changed

• (*) Implemented RFC 70. In both the Cedar and JSON schema syntaxes, it is now illegal to define the same entity name, common type name, or action name in both the empty namespace and a nonempty namespace.
• (*) Implemented RFC 52. Names containing __cedar (e.g., __cedar, A::__cedar, __cedar::A, and A::__cedar::B) are now invalid. (#969)
• The API around Request::new has changed to remove the Options around the entity type arguments. See RFC 55.
• Replaced uses of "natural", "human", "human-readable", and "custom" with "Cedar" (#1114). APIs with these names are changed accordingly. E.g., Schema::from_str_natural to Schema::from_cedarschema_str. Moreover, the FromStr implementations of Schema and SchemaFragment now parse strings in the Cedar schema format. Use Schema::from_json_str and SchemaFragment::from_json_str to parse strings in the JSON schema format.
• Significantly reworked all public-facing error types to address some issues and improve consistency. See issue #745.
• Finalized the ffi module and cedar-wasm crate which were preview-released in 3.2.0. This involved API breaking changes in both. See #757 and #854.
• (*) Changed policy validation to reject comparisons and conditionals between record types that differ in whether an attribute is required or optional. (#769)
• (*) Improved consistency between JSON and Cedar schema formats. Both now forbid using Bool, Boolean, Entity, Extension, Long, Record, Set, and String as common type names. (#1150, resolving #1139)
• Changed the FFI to error on typos or unexpected fields in the input JSON (#1041)
• Changed Policy::parse and Template::parse to accept an Option<PolicyId> instead of Option<String> to set the policy id (#1055, resolving #1049)
• PolicySet::template_annotation now returns Option<&str> as opposed to Option<String> in the previous version (#1131, resolving #1116)
• Moved <PolicyId as FromStr>::Err to Infallible (#588, resolving #551)
• Removed unnecessary lifetimes from some validation related structs (#715)
• Marked errors/warnings related to parsing and validation as non_exhaustive, allowing future variants to be added without a breaking change. (#1137, #1169)

Removed

• (*) Removed unspecified entity type. See RFC 55.
• Removed integration testing harness from the cedar-policy crate. It is now in an internal crate, allowing us to make semver incompatible changes. (#857)
• Removed the (deprecated) frontend module in favor of the new ffi module introduced in 3.2.0. See #757.
• Removed ParseErrors::errors_as_strings. Callers should consider examining the rich data provided by miette::Diagnostic, for instance .help() and labels(). Callers can continue using the same behavior by calling .iter().map(ToString::to_string). (#882, resolving #543)
• Removed ParseError::primary_source_span. Callers should use the location information provided by miette::Diagnostic via .labels() and .source_code() instead. (#908)
• Removed Display impl for EntityId in favor of explicit .escaped() and .as_ref() for escaped and unescaped representations (respectively) of the EntityId; see note there (#921, resolving #884)

Fixed

• (*) JSON format Cedar schemas will now fail to parse if they reference an unknown extension type. This was already an error for human-readable schema syntax. (#890, resolving #875)
• (*) Schemas can now reference entity and common types defined in the empty namespace, even in contexts occurring in a non-empty namespace. (#1060, resolving #579)

Release 3.4.3, available on crates.io

Fixed

• Slot identifiers are now checked for JSON policy templates using slots in is Type in ?slot scope constraints. Loading a JSON format policy using principal is Type in ?resource or resource is Type in ?principal. (#2351)

Cedar Language Version: 3.4

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 3.4

Fixed

• The schema format conversion method SchemaFragment::to_cedarschema will now return a name collision error when trying to convert a schema where any namespaced type name collides with an unqualified type. This avoids a situation where format conversion could change the target of an entity type reference. (#1212, resolving #1063) This does not change what schema are accepted by the parsing functions for either format.

Cedar Language Version: 3.4

Added

• Convenience methods num_of_policies() and num_of_templates() to see how many policies and templates a policy set has (#1180)
• Entity is now Hash. The hash implementation compares the hash of the entity UID (#1186)

Fixed

• (*) Entities::from_entities() will now correctly reject record attributes with superfluous attributes. (#1177, resolving #1176)

Cedar Language Version: 3.4

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 3.4

Added

• JSON representation for Policy Sets, along with methods like ::from_json_value/file/str and ::to_json for PolicySet. (#783, resolving #549)
• Methods for reading and writing individual Entitys as JSON (#924, resolving #807)
• Context::into_iter to get the contents of a Context and Context::merge to combine Contexts, returning an error on duplicate keys (#1027, resolving #1013)
• Several new APIs for schemas to allow accessing principal and resource types, action entity uids, etc. (#1141, resolving #1134)

Changed

• Added deprecation warnings to APIs that will be removed in the upcoming 4.0 release, as well as wrapper methods with the new names, where appropriate. See the notes under that release for more details. (#1128)
• Reduced precision of partial evaluation for ||, &&, and conditional expressions. if { foo : <unknown> }.foo then 1 + "hi" else false now evaluates to if <unknown> then 1 + "hi" else false. (#874)
• Removed the error extension function, which was previously used during partial evaluation. (#874)

Fixed

• (*) JSON format Cedar policies will now fail to parse if the action scope constraint contains a non-action entity type, matching the behavior for human-readable Cedar policies. (#943, resolving #925)
• Template parsing functions (e.g., Template::parse()) will now fail when passed a static policy as input. Use the Policy parsing functions instead. (#1108, resolving #1095)

Cedar Language Version: 3.3

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 3.3

Note: 3.2.2 and 3.2.3 skipped to maintain consistency with the cedar-wasm package

Fixed

• (*) JSON format Cedar policies will now fail to parse if any annotations are not valid Cedar identifiers. (#1004, resolving #994)
• (*) unknown() is no longer a valid extension function if partial-eval is not enabled as a feature. (#1101, resolving #1096)

Cedar Language Version: 3.3

Fixed

• Fixed policy formatter dropping newlines in string literals. (#870, #910, resolving #862)
• Fixed a performance issue when constructing an error for accessing a non-existent attribute on sufficiently large records (#887, resolving #754)
• Fixed identifier parsing in human-readable schemas (#914, resolving #913)
• Fixed the typescript generated type for ffi::AuthorizationCall to remove unsupported string option (#939)
• Fixed Wasm build script to be multi-target in JS ecosystem (#933)

Cedar Language Version: 3.3

Added

• Expression::new_ip, Expression::new_decimal, RestrictedExpression::new_ip, and RestrictedExpression::new_decimal (#661, resolving #659)
• Entities::into_iter (#713, resolving #680)
• Entity::into_inner (#685, resolving #636)
• New ffi module with an improved FFI interface. This will replace the frontend module in the 4.0 release, but is available now for early adopters; the frontend module is now deprecated. This should be considered a preview-release of ffi; more API breaking changes are anticipated for Cedar 4.0. (#852)
• wasm Cargo feature for targeting Wasm (and the cedar-wasm crate was added to this repo). This should be considered a preview-release of cedar-wasm; more API breaking changes are anticipated for Cedar 4.0. (#858)

Changed

• Common type definitions in both human-readable and JSON schemas may now reference other common type definitions. There may not be any cycles formed by these references. (#766, resolving #154)
• Improved validation error messages when incompatible types appear in if, ==, contains, containsAll, and containsAny expressions. (#809, resolving #346)
• Deprecated error TypeErrorKind::ImpossiblePolicy in favor of warning ValidationWarningKind::ImpossiblePolicy so future improvements to Cedar typing precision will not result in breaking changes. (#716, resolving #539)
• Rework API for the partial-eval experimental feature (#714, #817, #838).
• Validation errors for unknown entity types and action entities now report the precise source location where the unknown type was encountered. Error for invalid use of an action now includes a source location containing the offending policy. (#802, #808, resolving #522)
• Deprecated the frontend module in favor of the new ffi module. The frontend module will be removed from cedar-policy in the next major version. See notes above about ffi. (#852)
• Deprecated the integration testing harness code. It will be removed from the cedar-policy crate in the next major version. (#707)

Fixed

• Validation error message for an invalid attribute access now reports the correct attribute and entity type when accessing an optional attribute that is itself an entity. (#811)
• The error message returned when parsing an invalid action scope constraint action == ?action no longer suggests that action == [...] would be a valid scope constraint. (#818, resolving #563)
• Fixed policy formatter reordering some comments around if-then-else and entity identifier expressions. (#861, resolving #787)

Cedar Language Version: 3.2

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 3.2

Fixed

• The formatter will now fail with an error if it changes a policy's semantics. (#865)

Cedar Language Version: 3.2

Changed

• Improve parser errors on unexpected tokens. (#698, partially resolving #176)
• Validation error messages render types in the new, more readable, schema syntax. (#708, resolving #242)
• Improved error messages when null occurs in entity json data. (#751, resolving #530)
• Improved source location reporting for error found template slot in a when clause. (#758, resolving #736)
• Improved Display implementation for Cedar schemas, both JSON and human syntax. (#780)

Fixed

• Support identifiers in context declarations in the human-readable schema format. (#734, resolving #681)

Cedar Language Version: 3.2

Changed

• Implement RFC 57: policies can now include multiplication of arbitrary expressions, not just multiplication of an expression and a constant.

Cedar Language Version: 3.1

Fixed

• ValidationResult methods validation_errors and validation_warnings, along with confusable_string_checker, now return iterators with static lifetimes instead of custom lifetimes, fixing build for latest nightly Rust. (#712)
• Validation for the in operator to no longer reports an error when comparing actions in different namespaces. (#704, resolving #642)

Cedar Language Version: 3.1

Added

• Implementation of the human-readable schema format proposed in RFC 24. New public APIs SchemaFragment::from_*_natural, SchemaFragment::as_natural, and Schema::from_*_natural (#557)
• PolicyId::new() (#587, resolving #551)
• EntityId::new() (#583, resolving #553)
• AsRef<str> implementation for PolicyId (#504, resolving #503)
• Policy::template_links() to retrieve the linked values for a template-linked policy (#515, resolving #489)
• AuthorizationError::id() to get the id of the policy associated with an authorization error (#589)
• For the partial-eval experimental feature: added Authorizer::evaluate_policies_partial() (#593, resolving #474)
• For the partial-eval experimental feature: added json_is_authorized_partial() (#571, resolving #570)

Changed

• Better integration with miette for various error types. If you have previously been just using the Display trait to get the error message from a Cedar error type, you may want to consider also examining other data provided by the miette::Diagnostic trait, for instance .help(). Alternately, you can use miette and its fancy feature to format the error and all associated information in a pretty human-readable format or as JSON. For more details, see miette's documentation. (#477)
• Cedar reserved words like if, has, and true are now allowed as policy annotation keys. (#634, resolving #623)
• Add hints suggesting how to fix some type errors. (#513)
• The ValidationResult returned from Validator::validate now has a static lifetime, allowing it to be used in more contexts. The lifetime parameter will be removed in a future major version. (#512)
• Improve parse error around invalid is expressions. (#491, resolving #409)
• Improve parse error message when a policy includes an invalid template slot. The error now identifies that the policy used an invalid slot and suggests using one of the valid slots. (#487, resolving #451)
• Improve parse error messages to more reliably notice that a function or method does exist when it is called with an incorrect number of arguments or using the wrong call style. (#482)
• Include source spans on more parse error messages. (#471, resolving #465)
• Include source spans on more evaluation error messages. (#582)
• Changed error message on SchemaError::UndeclaredCommonTypes to report fully qualified type names. (#652, resolving #580)
• For the partial-eval experimental feature: make the return values of RequestBuilder's principal, action, resource, context and schema functions #[must_use]. (#502)
• For the partial-eval experimental feature: make RequestBuilder::schema return a RequestBuilder<&Schema> so the RequestBuilder<&Schema>::build method checks the request against the schema provided and the RequestBuilder<UnsetSchema>::build method becomes infallible. (#591, resolving #559)
• For the permissive-validate experimental feature: X in [] is typed False for all X, including unspecified X. (#615)

Fixed

• Action entities in the store will pass schema-based validation without requiring the transitive closure to be pre-computed. (#581, resolving #285)
• Variables qualified by a namespace with a single element are correctly rejected. E.g., foo::principal is an error and is not parsed as principal. Variables qualified by a namespace of any size comprised entirely of Cedar keywords are correctly rejected. E.g., if::then::else::principal is an error. (#594 and #597)
• The entity type tested for by an is expression may be an identifier shared with a builtin variable. E.g., ... is principal and ... is action are now accepted by the Cedar parser. (#595, resolving #558)
• Policies containing the literal i64::MIN can now be properly converted to the JSON policy format. (#601, resolving #596)
• Policy::to_json does not error on policies containing special identifiers such as principal, then, and true. (#628, resolving #604)
• Template::from_json errors when there are slots in template conditions. (#626, resolving #606)

Cedar Language Version: 3.0

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 3.0

Fixed

• Possible panic (when stack size limit reached) in Context::empty() (#524, fixed by #526)

Cedar Language Version: 3.0

Added

• The is operation as described in RFC 5. (#396)
• Marked the Template::from_json and Template::to_json apis as public (#458)
• New APIs to Entities to make it easy to add a collection of entities to an existing Entities structure. (#276)
• PolicySet::remove_static, PolicySet::remove_template and PolicySet::unlink to remove policies from the policy set. (#337, resolving #328)
• PolicySet::get_linked_policies to get the policies linked to a Template. (#337)
• Export the cedar_policy_core::evaluator::{EvaluationError, EvaluationErrorKind} and cedar_policy_core::authorizer::AuthorizationError error types. (#260, #271)
• ParseError::primary_source_span to get the primary source span locating an error. (#324)
• ValidationResult::validation_warnings to access non-fatal warnings returned by the validator and ValidationResult::validation_passed_without_warnings. The main validation entry point now checks for warnings previously only available through confusable_string_checker. (#404)
• Entity::new_no_attrs() which provides an infallible constructor for Entity in the case that there are no attributes. (See changes to Entity::new() below.) (#430)
• RestrictedExpression::new_entity_uid() (#442, resolving #350)
• Experimental API PolicySet::unknown_entities to collect unknown entity UIDs from a PartialResponse. (#353, resolving #321)

Changed

• Implement RFC 19, making validation slightly more strict, but more explainable. (#282)
• Implement RFC 20, disallowing duplicate keys in record values (including record literals in policies, request context, and records in entity attributes). (#375)
• Request::new() now takes an optional schema argument, and validates the request against that schema. To signal validation errors, it now returns a Result. (#393, resolving #191)
• Entities::from_*() methods now automatically add action entities present in the schema to the constructed Entities, if a schema is provided. (#360)
• Entities::from_*() methods now validate the entities against the schema, if a schema is provided. (#360)
• Entities::from_entities() and Entities::add_entities() now take an optional schema argument. (#360)
• Diagnostics::errors() now returns an iterator over AuthorizationErrors. (#260)
• Response::new() now expects a Vec<AuthorizationError> as its third argument. (#260)
• Change the semantics of equality for IP ranges. For example, ip("192.168.0.1/24") == ip("192.168.0.3/24") was previously true and is now false. The behavior of equality on single IP addresses is unchanged, and so is the behavior of .isInRange(). (#348)
• Standardize on duplicates being errors instead of last-write-wins in the JSON-based APIs in the frontend module. This also means some error types have changed. (#365, #448)
• Entity::new() now eagerly evaluates entity attributes, leading to performance improvements (particularly when entity data is reused across multiple is_authorized calls). As a result, it returns Result, because attribute evaluation can fail. (#430)
• Entities::from_json_*() also now eagerly evaluates entity attributes, and as a result returns errors when attribute evaluation fails. (#430)
• Entity::attr() now returns errors in many fewer cases (because the attribute is stored in already-evaluated form), and its error type has changed. (#430)
• Context::from_*() methods also now eagerly evaluate the Context, and as a result return errors when evaluation fails. (#430)
• Rename cedar_policy_core::est::EstToAstError to cedar_policy_core::est::FromJsonError. (#197)
• Rename cedar_policy_core::entities::JsonDeserializationError::ExtensionsError to cedar_policy_core::entities::JsonDeserializationError::ExtensionFunctionLookup. (#360)
• Rename variants in SchemaError. (#231)
• SchemaError has a new variant corresponding to errors evaluating action attributes. (#430)
• Improve schema parsing error messages when a cycle exists in the action hierarchy to includes an action which is part of the cycle (#436, resolving #416).
• <EntityId as FromStr>::Error is now Infallible instead of ParseErrors. (#372)
• Improve the Display impls for Policy and PolicySet, and add a Display impl for Template. The displayed representations now more closely match the original input, whether the input was in string or JSON form. (#167, resolving #125)
• ValidationWarning::location and ValidationWarning::to_kind_and_location now return &SourceLocation<'a> instead of &'a PolicyID, matching ValidationError::location. (#405)
• ValidationWarningKind is now non_exhaustive, allowing future warnings to be added without a breaking change. (#404)

Fixed

• Evaluation order of operand to > and >=. They now evaluate left to right, matching all other operators. This affects what error is reported when there is an evaluation error in both operands, but does not otherwise change the result of evaluation. (#402, resolving #112)
• Updated PolicySet::link to not mutate internal state when failing to link a static policy. With this fix it is possible to create a link with a policy id after previously failing to create that link with the same id from a static policy. (#412)
• Fixed schema-based parsing of entity data that includes unknowns (for the partial-eval experimental feature). (#419, resolving #418)

Removed

• Removed __expr escape from Cedar JSON formats, which has been deprecated since Cedar 1.2. (#333)
• Move ValidationMode::Permissive behind an experimental feature flag. To continue using this feature you must enable the permissive-validate feature flag. (#428)

Cedar Language Version: 2.2

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 2.2

Added

• Convenience methods num_of_policies() and num_of_templates() to see how many policies and templates a policy set has (#1180)

Cedar Language Version: 2.2

Fixed

• Fixed parsing of small negative decimal literals. (#1964)

Cedar Language Version: 2.2

Fixed

• Fixed policy formatter reordering some comments around if-then-else and entity identifier expressions. (#861, resolving #787)
• Fixed policy formatter dropping newlines in string literals. (#870, #910, resolving #862)

Cedar Language Version: 2.2

Fixed

• The formatter will now fail with an error if it changes a policy's semantics. (#865)

Cedar Language Version: 2.2

Changed

• Implement RFC 57: policies can now include multiplication of arbitrary expressions, not just multiplication of an expression and a constant.