Skip to content

chore: decompose finding SEC-21 into atomic implementation subt - #232

Open
esafwan wants to merge 2 commits into
developfrom
task/SweepSecurity-SEC-21-decompose
Open

chore: decompose finding SEC-21 into atomic implementation subt#232
esafwan wants to merge 2 commits into
developfrom
task/SweepSecurity-SEC-21-decompose

Conversation

@esafwan

@esafwan esafwan commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

What it does / Summary

Decomposes security finding SEC-21 into an actionable, structured implementation subtask by generating plans/SweepSecurity:SEC-21-plan.json.

What it solves / Motivation

  • Establishes scope and acceptance criteria for adding authorization guards to release_tables_after_print(invoice).
  • Ensures table clusters are only released when the caller is authorized for the target POS Invoice and assigned to its branch.

Key Technical Changes

  • Created plans/SweepSecurity:SEC-21-plan.json specifying:
    • Objective: Add authorization checks to release_tables_after_print(invoice) scoped to the invoice's branch/table cluster.
    • Acceptance Criteria: Reject unauthorized table release requests while continuing to release occupied table clusters for authorized callers.
    • Scope: ury/ury/doctype/ury_order/ury_order.py.
    • Metadata: Task type impl, difficulty 2, risk 2, uncertainty 2, priority 80.

@esafwan esafwan changed the title Decompose SweepSecurity finding SEC-21 into atomic implementation subt chore: decompose finding SEC-21 into atomic implementation subt Jul 21, 2026
…-21)

- Added authorization checks to `release_tables_after_print`.
- Restricted table release to users with write access to the target POS Invoice.
- Prevented unauthorized table release requests while preserving existing behavior for authorized users.
@ShahalaKP-Tridz
ShahalaKP-Tridz marked this pull request as ready for review July 29, 2026 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants