Skip to content

pup: enable OAuth for ASM WAF commands - #757

Draft
srosenthal-dd wants to merge 1 commit into
DataDog:mainfrom
srosenthal-dd:stephen.rosenthal/oauth-asm-waf
Draft

pup: enable OAuth for ASM WAF commands#757
srosenthal-dd wants to merge 1 commit into
DataDog:mainfrom
srosenthal-dd:stephen.rosenthal/oauth-asm-waf

Conversation

@srosenthal-dd

@srosenthal-dd srosenthal-dd commented Aug 24, 2026

Copy link
Copy Markdown
Member

Summary

Switch 10 ASM WAF functions in security.rs from make_api_no_auth! to make_api! so they send the OAuth bearer token. Add appsec_protect_read and appsec_protect_write to the OAuth scope list in auth/types.rs.

Server-side dependency

The ASM WAF routes are in dd-go's rc-api service (chi router, JWT-based auth from the API gateway). The server-side gap is at the gateway level -- the rc-api service itself has no per-route authn method configuration. This is blocked pending investigation with the remote-config team (DAL-743).

Changes

  • src/commands/security.rs: 10 make_api_no_auth! -> make_api! swaps (5 asm_custom_rules_* + 5 asm_exclusions_*)
  • src/auth/types.rs: Added appsec_protect_read and appsec_protect_write to the OAuth scope list

Switch 10 ASM WAF functions in security.rs from make_api_no_auth!
to make_api! so they send the OAuth bearer token. Add appsec_protect_read
and appsec_protect_write to the OAuth scope list in auth/types.rs.

Server-side dependency: the ASM WAF routes in dd-go rc-api need to
accept OAuth at the gateway level. This is currently blocked pending
investigation with the remote-config team (DAL-743).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant