Skip to content

fix(api): use userInternalUUID for addon invocation auth context#112

Merged
ericfitz merged 1 commit intomainfrom
fix/addon-invocation-auth-context
Jan 23, 2026
Merged

fix(api): use userInternalUUID for addon invocation auth context#112
ericfitz merged 1 commit intomainfrom
fix/addon-invocation-auth-context

Conversation

@ericfitz
Copy link
Owner

Summary

  • Fixed InvokeAddon handler to use userInternalUUID instead of userID from context
  • The userID context value contains the provider user ID string (e.g., alice@tmi.local), not a UUID
  • This caused 401 "Invalid authentication context" errors when invoking addons
  • Also updated diagram_model_transform.go to remove SecurityBoundary field references that were removed from the OpenAPI spec

Test plan

  • make lint passes
  • make build-server passes
  • make test-unit passes
  • Manual test: Invoke addon via client, verify no 401 error

🤖 Generated with Claude Code

The InvokeAddon handler was incorrectly using "userID" from context (which
contains the provider user ID string like alice@tmi.local) instead of
"userInternalUUID" (which contains the actual UUID). This caused 401 errors
with "Invalid authentication context" when users tried to invoke addons.

Also updates diagram_model_transform.go to remove SecurityBoundary field
references that were removed from MinimalNode and Node_Data types in the
OpenAPI spec update.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@dosubot dosubot bot added the bug Something isn't working label Jan 23, 2026
@ericfitz ericfitz merged commit 46dee7c into main Jan 23, 2026
7 checks passed
@ericfitz ericfitz deleted the fix/addon-invocation-auth-context branch January 23, 2026 03:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant