Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 17:36:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
bcquality/custom/knowledge/security/cmfrt-three-permissionset-pattern.md
BeytullahCengiz88 afb1fa2883 Add CMFRT naming conventions, object ID ranges, and patterns documentation 
- Introduced guidelines for using the "CMFRT" prefix in object names, fields, and procedures to avoid naming collisions and ensure clarity.
- Established rules for object ID ranges to prevent conflicts with other extensions and maintain historical integrity.
- Documented best practices and anti-patterns for various coding patterns, including case statements, interface injection, label usage, and validation methods.
- Implemented a standards review skill to evaluate AL source changes against CMFRT company standards, ensuring compliance with naming, permissions, and architectural patterns.
2026-07-14 14:09:04 +02:00

1.7 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
all
security
permissionset
permission-set
objects
read
edit
assignable
included-permission-sets
authorization
al
w1
all

CMFRT three-permission-set pattern

Description

Every CMFRT functional module must ship exactly three permission set objects: an Objects set, a Read set, and an Edit set. The Objects set lists every AL object the module owns — tables, pages, codeunits, reports, interfaces — with X (execute) access. The Read set includes the Objects set via IncludedPermissionSets and grants tabledata = R on each table. The Edit set includes the Read set and grants tabledata = IMD on each writable table. All three sets have Assignable = true. Names follow the pattern "CMFRT <ABBR> Objects", "CMFRT <ABBR> Read", and "CMFRT <ABBR> Edit".

Best Practice

Define the sets in the strict composition chain Objects ← Read ← Edit so that object access is declared once and inherited. When a new table is added to the module, update the Objects set and the tabledata entries in Read and Edit — there is no risk of the object access drifting between roles because the chain is the single source of truth for it.

See sample: cmfrt-three-permissionset-pattern.good.al.

Anti Pattern

Shipping fewer than three permission sets, omitting IncludedPermissionSets and enumerating the same object list in each set by hand, or granting RIMD access in a flat set that cannot be composed. Flat role sets that enumerate objects independently drift apart when tables are added or removed, and the resulting authorization gap is invisible until a user reports an access error in production.

See sample: cmfrt-three-permissionset-pattern.bad.al.