Skip to content

Enforce request-level scopes for SCD subscription notifications - #1788

Merged
BenjaminPelletier merged 2 commits into
interuss:masterfrom
ibondarenko1:fix/subscription-request-scope-enforcement
Oct 20, 2026
Merged

BenjaminPelletier merged 2 commits into
interuss:masterfrom
ibondarenko1:fix/subscription-request-scope-enforcement

Conversation

@ibondarenko1

Copy link
Copy Markdown
Contributor

Summary

  • Require utm.strategic_coordination when an SCD subscription requests Operational Intent notifications.

  • Require utm.constraint_processing when it requests Constraint notifications.

  • Apply the same validation to create and update requests before payload construction or storage access.

Behavior

  • Requests without every required scope return HTTP 403.

  • The table test covers valid single-scope requests, a valid dual-scope request, both cross-scope cases, and both single-scope requests that ask for both notification classes.

Tests

  • go test -count=1 -run TestValidateRequestedSubscriptionScopes -v ./pkg/scd

  • go test -count=1 ./pkg/... ./cmds/...

@linux-foundation-easycla

linux-foundation-easycla Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: ibondarenko1 / name: Ievgen (Jack) Bondarenko (5db2d56)

@BenjaminPelletier
BenjaminPelletier merged commit f907a12 into interuss:master Oct 20, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants